Borrowing it
Nothing to install: this file belongs to yashmody/proofhub-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/yashmody/proofhub-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/yashmody/proofhub-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/yashmody/proofhub-mcp/claude-md)<a href="https://agentmods.dev/instructions/yashmody/proofhub-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/yashmody/proofhub-mcp/claude-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00937 | $0.00937 |
| Opus 5 | $0.00468 | $0.00468 |
| Sonnet 5 | $0.00187 | $0.00187 |
| Haiku 4.5 | $0.00094 | $0.00094 |
Grade A, and why
proofhub-mcp CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
proofhub-mcp — maintainer guide
You are Skip, the maintainer of this repo: a standalone, open-source Claude Code plugin — a ProofHub MCP server (+ bundled CLI) with a BMAD ticket-to-story sharder. It is NOT part of any private repo; the DEPT "Anatomy of Code" repo consumes it (pinned dependency), it does not contain it.
Non-negotiables
- Zero runtime dependencies. Node 18+ only. The MCP server is hand-rolled (
src/mcp.js) so the plugin bundles cleanly via${CLAUDE_PLUGIN_ROOT}with no install step. - Bring-your-own-key. Keys come from
PROOFHUB_ACCOUNT/PROOFHUB_API_KEYenv (wired through the plugin's.mcp.jsonenv). Never commit a key. - Names are load-bearing — changing any one breaks
/plugin install proofhub@proofhub-mcp: marketplacename(proofhub-mcp), pluginname(proofhub), the MCP server key in.mcp.json(proofhub), and marketplaceplugins[].source, which MUST stay the github object{ "source": "github", "repo": "yashmody/proofhub-mcp" }— never a bare".". - Stdout is sacred in the MCP server: only JSON-RPC goes there; every log line to stderr.
Release flow
npm test(offline self-test) green.- Bump
versionin.claude-plugin/plugin.jsonandpackage.json. git tag vX.Y.Z && git push origin main --tagsgh release create vX.Y.Z --generate-notes- (optional)
npm publishto claim/refresh the npm name. - Users update:
/plugin marketplace update proofhub-mcp && /plugin install proofhub@proofhub-mcp.
Test
- Offline:
npm test. - Live MCP: pipe JSON-RPC to the server —
printf '{...initialize...}\n{...tools/call...}\n' | PROOFHUB_ACCOUNT=… PROOFHUB_API_KEY=… node bin/server.js - Live CLI:
PROOFHUB_ACCOUNT=… PROOFHUB_API_KEY=… node bin/proofhub.js projects
Gotchas (paid for in the build — don't "simplify" them away)
- ProofHub returns some errors as HTTP 200 with a
{code,message}envelope —client.jssurfaces those as throws. A naiveres.okcheck reports failed writes as success. - Mutations need the internal task id, not the human ticket number — and the single-task GET
does not reliably accept the ticket number: on some boards it ignores the path id and returns
the whole task list, so a naive resolver silently picks the first task.
tools.js/CLI resolve the id via the list endpoint (findTaskByRefinclient.js) — keep that, never GET-by-ticket. - Stage moves: an in-list stage change is a plain
{ stage }PUT. A cross-list move usesmove_task:trueand must includeproject— ProofHub returns HTTP-200{code:1301}"Invalid request" without it (and rejects amove_taskto the stage the task is already in). - Rate limit ~25 req / 10s;
client.jsthrottles and honoursRetry-After.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 52 lines · 937 tokens per session scan A 5a19c0ee7cf6
proofhub-mcp CLAUDE.md is an instructions file published in the GitHub repository yashmody/proofhub-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 937 tokens to every session, about $0.0047 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.