Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/todevelopers/fogbugz-mcp/claude-mdgit clone --depth 1 https://github.com/todevelopers/fogbugz-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/todevelopers/fogbugz-mcp/claude-md)<a href="https://agentmods.dev/instructions/todevelopers/fogbugz-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/todevelopers/fogbugz-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 | $0.01165 | $0.01165 |
| Opus 5 | $0.00583 | $0.00583 |
| Sonnet 5 | $0.00233 | $0.00233 |
| Haiku 4.5 | $0.00117 | $0.00117 |
Grade A, and why
fogbugz-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 4d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project rules
Versioning
Before creating a git tag, always update the version in both files to match the tag:
package.json→"version"manifest.json→"version"
Example: tag v0.0.3 → both files must have "version": "0.0.3".
Version increment rules:
- Always increment the PATCH version (third number) by default:
0.0.9→0.0.10. - Only increment MINOR (second number) or MAJOR (first number) when explicitly instructed by the user.
Language
All content in this repository must be written in English — code, comments, commit messages, documentation, and planning files. No other language is permitted.
Company name
The correct legal name of the company is ToDevelopers s.r.o. — always use this full name in legal or formal contexts (LICENSE, package.json author, manifest author). The short form ToDevelopers is acceptable in UI-facing fields such as display_name and author.name in the manifest.
Tool naming
Tool names must never use a fogbugz_ prefix. Use plain descriptive names only (e.g. create_case, search_cases). This applies to all new tools added to src/commands/tools.ts.
Tool definition checklist (QA)
Every tool added to src/commands/tools.ts must satisfy all of the following:
Required fields
name— plain snake_case, nofogbugz_prefixtitle— short human-readable label shown in Claude's tool picker (e.g.'Create Case')description— one sentence explaining what the tool does plus 1–2 concrete usage examples inlineinputSchema— valid JSON Schema object withtype,properties, andrequiredannotations— always present, never omitted
Annotations rules
| Tool type | readOnlyHint |
destructiveHint |
|---|---|---|
| Read-only (list, get, search, view) | true |
omit or false |
| Write / mutating (create, update, assign, resolve, reopen, close) | false |
true |
| Generic / raw API pass-through | false |
true |
// Read-only example
annotations: { readOnlyHint: true }
// Mutating example
annotations: { readOnlyHint: false, destructiveHint: true }
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.
- 4d ago First seen · 112 lines · 1,165 tokens per session scan A f83f9f432459
fogbugz-mcp CLAUDE.md is an instructions file published in the GitHub repository todevelopers/fogbugz-mcp (2 stars, last pushed 2mo ago), licensed MIT. It adds 1,165 tokens to every session, about $0.0058 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
cowork--bug-reporter CLAUDE.md
Instructions for cpinto/cowork--bug-reporter, covering bug reporting from video walkthroughs, configuration, ground rules, environment and workflow.
llm-context.py CLAUDE.md
Instructions for cyberchitta/llm-context.py, covering claude.md, working notes (gitignored) and draining the field notes.
mcp-erpnext CLAUDE.md
Claude Code instructions for Casys-AI/mcp-erpnext: See AGENTS.md for all repository guidelines, architecture, conventions, and task recipes.
markifact-mcp GEMINI.md
Instructions for markifact/markifact-mcp, covering markifact, the 8 tools, discover → inspect → run, connection vs account and reporting workflow.
student-llm-wiki AGENTS.md
Instructions for IssacW228/student-llm-wiki, covering student llm wiki — agent instructions, 操作规则 operation rules, token预算规则(最高优先级), 架构 architecture and 命令 commands.
rag-code-mcp copilot-instructions.md
Instructions for doITmagic/rag-code-mcp, covering copilot instructions - ragcode mcp, ⚖️ the golden rule, project overview, architecture & patterns and developer workflows.