Development

octocode-harness-status - Claude MCP Skill

Show all skills, MCP servers, CLIs, and tokens installed on this machine per vendor in an interactive HTML dashboard. Opens in the default browser. Allows removing MCPs from config files and deleting skill folders directly from the UI. Use when the user asks to "show my harness", "check installed skills", "show my MCPs", "check my AI setup", "show all agents", "harness status", "what CLIs are installed", "check token limits", "review my agent context", or wants an inventory of their full AI tooling.

SEO Guide: Enhance your AI agent with the octocode-harness-status tool. This Model Context Protocol (MCP) server allows Claude Desktop and other LLMs to show all skills, mcp servers, clis, and tokens installed on this machine per vendor in an interactiv... Download and configure this skill to unlock new capabilities for your AI workflow.

๐ŸŒŸ26 stars โ€ข 73 forks
๐Ÿ“ฅ0 downloads

Documentation

SKILL.md
# Octocode Harness Status

Audit every agent vendor on this machine, measure skill context budget, and expose one-click removal โ€” all in a local interactive browser dashboard.

## When to Activate

- "Show my harness", "harness status", "show my AI setup"
- "What skills/MCPs are installed?", "check all vendors"
- "What CLIs are installed and authenticated?"
- "How much context do my skills use?"
- "Remove a skill or MCP", "clean up my agent config"

## Workflow

**One command. That's it.**

```bash
node skills/octocode-harness-status/scripts/build_harness.mjs
```

The script:
1. Reads MCP configs for all supported vendors (Cursor, Claude Code, Claude Desktop, Windsurf, Antigravity, Zed, Codex, Gemini CLI, Kiro, Goose, Trae, VS Code Cline/Roo/Continue, Opencode)
2. Scans all skill directories per vendor
3. Checks installed CLIs and auth status (octocode-cli, gh, claude, cursor, gemini, codex, goose, opencode)
4. Queries GitHub token rate limits
5. Measures SKILL.md context load per vendor and rates it vs typical agent context windows
6. Starts a local HTTP server, opens the dashboard in your default browser
7. Handles live remove/delete actions from the dashboard UI

### Flags

| Flag | Description | Default |
|------|-------------|---------|
| `--port <n>` | HTTP server port | auto (random free port) |
| `--no-open` | Generate but don't open browser | opens |
| `--timeout <s>` | Server auto-shutdown after N seconds | 300 |
| `--help` | Print usage | โ€” |

### Dashboard sections

| Section | What it shows |
|---------|---------------|
| **Summary bar** | Vendor count, total MCPs, total skills, auth status |
| **Per-vendor cards** | MCP list + Skills list, each with a โœ• remove button |
| **CLI inventory** | Version, auth state, rate limits for each CLI |
| **Context budget** | Total SKILL.md bytes per vendor, estimated tokens, % of agent context window, colour-coded health |

### Context rating scale

| Colour | Budget used | Meaning |
|--------|-------------|---------|
| ๐ŸŸข Green | < 5 % | Lean โ€” almost no context overhead |
| ๐ŸŸก Yellow | 5โ€“15 % | Moderate โ€” normal for active setups |
| ๐ŸŸ  Orange | 15โ€“30 % | Heavy โ€” consider trimming inactive skills |
| ๐Ÿ”ด Red | > 30 % | Critical โ€” may crowd out useful context |

Context window baselines: Claude 200 k tokens ยท GPT-4o 128 k tokens ยท Gemini 1 M tokens ยท Codex 32 k tokens.

### Remove / edit actions (from the browser UI)

- **Remove MCP** โ€” deletes the server entry from the vendor's JSON config file (preserves other entries)
- **Edit MCP** โ€” edits command/args/type/env in place; **all other fields (`url`, `headers`, `disabled`, `autoApprove`, `cwd`, โ€ฆ) are preserved**, not dropped
- **Remove Skill** โ€” deletes the skill folder (`rm -rf`) from the vendor's skills directory
- **Delete script** โ€” deletes a single script file under the skill

Both actions prompt for confirmation in the dashboard before writing to disk.

**Read-only configs:** TOML (Codex) and YAML (Goose) configs are **parsed for display but never written** โ€” their MCP rows show a ๐Ÿ”’ and have no edit/remove buttons, so the dashboard can't corrupt non-JSON files.

**Safety:** the local server only accepts same-origin requests (no website you visit can drive it), rejects MCP/skill names containing path separators or `..`, and refuses to delete anything outside your home directory or any directory.

### Keyboard & navigation

- `/` โ€” focus the filter box
- `Esc` โ€” close any open modal
- **Expand all / Collapse all** โ€” toggle every vendor card at once

### Server lifecycle

The script prints the dashboard URL and keeps the server alive for `--timeout` seconds (default 5 min). Hit `Ctrl-C` or wait for auto-shutdown.

## Error handling

| Situation | Behaviour |
|-----------|-----------|
| Config file missing | Vendor shown as "not configured" โ€” no error |
| Skills directory missing | Skills count 0 โ€” no error |
| CLI not installed | CLI row shown as "not installed" |
| GitHub rate limit API unreachable | Rate limit shown as "N/A" |
| Port in use | Auto-increments to next free port |
| TOML (Codex) / YAML (Goose) config | Parsed read-only for display; MCP rows are locked (no edit/remove) |

Signals

Avg ratingโญ 0.0
Reviews0
Favorites0

Information

Repository
bgauryy/octocode-mcp
Author
bgauryy
Last Sync
6/21/2026
Repo Updated
6/19/2026
Created
6/18/2026

Reviews (0)

No reviews yet. Be the first to review this skill!

Related Skills

cursorrules

CrewAI Development Rules

โญ 43932Has guide

firecrawl-build-onboarding

Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.

โญ 39648

firecrawl-build-search

Integrate Firecrawl `/search` into product code and agent workflows. Use when an app needs discovery before extraction, when the feature starts with a query instead of a URL, or when the system should search the web and optionally hydrate result content.

โญ 39648

firecrawl-build

Integrate Firecrawl into application code whenever a product, agent, or workflow needs web data inside the app โ€” web search, live search results, page scraping, structured extraction, or browser interaction. Use when building any feature that needs data from the web in code, even if the user does not mention Firecrawl explicitly and only describes wanting web data, website content, search, scraping, or interaction in an application. Trigger for Firecrawl requests, "fire girl" shorthand, and generic app-level web-data needs that should map to `/scrape`, `/search`, or `/interact`. Do not use this skill for one-off terminal-only web tasks during the current session; use `firecrawl/cli` for those.

โญ 39648

Related Guides