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 commands/benshapyro/cadre-devkit-claude/backloggit clone --depth 1 https://github.com/benshapyro/cadre-devkit-claudeWrote 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/commands/benshapyro/cadre-devkit-claude/backlog)<a href="https://agentmods.dev/commands/benshapyro/cadre-devkit-claude/backlog"><img src="https://agentmods.dev/badge/commands/benshapyro/cadre-devkit-claude/backlog.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.00011 | $0.02635 |
| Opus 5 | $0.00005 | $0.01318 |
| Sonnet 5 | $0.00002 | $0.00527 |
| Haiku 4.5 | $0.00001 | $0.00264 |
Grade A, and why
backlog 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 — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backlog Mode
You are in Backlog Mode - documenting bugs and improvements WITHOUT implementing them.
Reference skills based on issue domain:
- API issues: Read
.claude/skills/api-design-patterns/SKILL.md - Frontend components: Read
.claude/skills/react-patterns/SKILL.md - Error handling: Read
.claude/skills/error-handler/SKILL.md - UX improvements: Read
.claude/skills/frontend-design/SKILL.md
Available Tools & When to Use Them
Codebase Exploration
Use Task tool with Explore subagent for:
- Finding root causes of bugs
- Understanding current implementation
- Locating affected files and components
Task(subagent_type="Explore", prompt="Very thorough: find all code related to [X]")
External Research
Use Exa search (mcp__exa__exa_search) for:
- Checking if others encountered the same bug
- Finding known fixes or workarounds
- Researching UI/UX best practices for similar features
mcp__exa__exa_search(query="[framework] [issue description] fix")
Use Ref documentation (mcp__Ref__*) for:
- Checking official framework/library docs
- Verifying correct API usage
- Finding recommended patterns
mcp__Ref__ref_search_documentation(query="[library] [feature] documentation")
UI/UX Verification
Use Playwright (mcp__playwright__*) for UX issues:
- Navigate to the affected page
- Take screenshot of current state (for BACKLOG entry)
- Verify the issue exists as user described
- Document "before" state
mcp__playwright__browser_navigate(url="http://localhost:3000/path")
mcp__playwright__browser_take_screenshot(filename="backlog-ux-xxx-before.png")
Complex Analysis
Use Sequential thinking (mcp__sequential-thinking__sequentialthinking) for:
- Multi-step root cause analysis
- Weighing multiple potential causes
- Structuring complex investigations
Parallel Execution Strategy
You CAN run multiple subagents AND tools in parallel by making multiple tool calls in a single message. Use this for efficiency when tasks are independent.
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 · 348 lines · 0 tokens per session scan A 2ceb5ccc4ffe
backlog is a command published in the GitHub repository benshapyro/cadre-devkit-claude (9 stars, last pushed 9mo ago), licensed MIT. It adds 11 tokens to every session and 2,635 once invoked, about $0.0001 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 commands, from other repositories
project-recap
Generate a visual project recap for context switching.
os-meeting
快速创建和管理AI团队会议.
workspace
Testany Workspace, 管理工作空间，成员权限，团队组织.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).
triage-issues
Launch the Issue Triage Agent (Haiku) to categorize and prioritize GitHub issues.