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/radleta/backlog.md-mcp/claude-mdgit clone --depth 1 https://github.com/radleta/Backlog.md-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/radleta/backlog.md-mcp/claude-md)<a href="https://agentmods.dev/instructions/radleta/backlog.md-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/radleta/backlog.md-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.00521 | $0.00521 |
| Opus 5 | $0.00260 | $0.00260 |
| Sonnet 5 | $0.00104 | $0.00104 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
Backlog.md-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 5d 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.
What it actually says
Backlog.md MCP Server - Claude Instructions
Documentation Organization
@.github/README.md @README.md
Important: The documentation above is organized by audience:
- .github/README.md - For developers contributing to the MCP server codebase (includes development setup, testing, and architecture)
- README.md - For users installing and using the MCP server (displayed on npm package page)
- CLAUDE.md (this section) - Claude-specific context and guidance
Claude-Specific Context
Understanding Your Audiences
When helping with this project, identify which audience you're serving:
- Users want to install and use the MCP server with their Backlog.md projects
- Developers want to contribute to or modify the MCP server codebase itself
Effective Task Management Guidance
When using the Backlog.md tools, always consider:
- Acceptance Criteria - Define measurable completion conditions
- Dependencies - Set execution order between related tasks
- Sub-tasks - Break complex work into manageable pieces
- Priority - Indicate task importance (high/medium/low)
Example workflow:
- Create parent task for major feature
- Add sub-tasks for implementation steps
- Set dependencies between sub-tasks
- Include acceptance criteria for each task
- Use sequence_list to verify execution order
Implementation Notes
Some features are MCP enhancements beyond the native CLI:
- Label filtering in task_list: O(n) calls - expensive for large task lists
- Decision operations: Efficient - direct filesystem access
- Resource aggregation: Multiple CLI calls with in-memory processing
Most operations are direct CLI pass-through for data integrity.
Key Points to Remember
- The MCP server is a wrapper around Backlog.md CLI - it doesn't implement custom write logic
- All security measures preserve user content (escape, don't remove)
- Interactive commands (like
backlog init) cannot be implemented through MCP - For Claude Code setup, users should use:
claude mcp add backlog-md -- backlog-mcp start - Development documentation is now in .github/README.md, user documentation is in README.md
- You can actively test the MCP server in your current session using
backlog-mcp-devmcp commands. If it doesn't exist, ask the user to install it viaclaude mcp add backlog-md-dev -- /path/to/local/repo/bin/backlog-mcp-dev.js start
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.
- 5d ago First seen · 52 lines · 521 tokens per session scan A 61893a8d733a
Backlog.md-mcp CLAUDE.md is an instructions file published in the GitHub repository radleta/Backlog.md-mcp (5 stars, last pushed 9mo ago), licensed MIT. It adds 521 tokens to every session, about $0.0026 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
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).
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.
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 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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.