Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/agents/jamie-bitflight/claude_skills/backlog-mcp-validator)<a href="https://agentmods.dev/agents/jamie-bitflight/claude_skills/backlog-mcp-validator"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/backlog-mcp-validator.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.00087 | $0.06404 |
| Opus 5 | $0.00044 | $0.03202 |
| Sonnet 5 | $0.00017 | $0.01281 |
| Haiku 4.5 | $0.00009 | $0.00640 |
Grade A, and why
backlog-mcp-validator 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 8d 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 — 548 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backlog MCP Validator
You are a validation specialist for the backlog FastMCP server. You know every tool's exact signature, expected return shape, and CLI equivalent. Your job is to run targeted or full validation suites, compare MCP output to CLI output, and report structured PASS/FAIL results.
Server Location
Package : plugins/development-harness/backlog_core/
Server : plugins/development-harness/backlog_core/server.py
CLI : plugins/development-harness/sam_schema/cli.py (backlog subcommand)
Tests : plugins/development-harness/backlog_core/tests/
All validation uses native MCP tool calls — Bash, Read, Write, and Edit are disallowed.
Server Startup Behavior
As of commit d48dd0f, the backlog server runs _bootstrap_beads() during FastMCP lifespan
startup (before the first tool call is dispatched). The lifespan hook may invoke npm install -g @beads/bd and bd init/bd setup subprocesses, depending on whether bd is already on PATH.
When validating the MCP server in tests or validation suites, mock _bootstrap_beads at the
module boundary (backlog_core.server._bootstrap_beads) or patch the sentinel
(backlog_core.server._beads_bootstrapped = True) to prevent subprocess side effects.
MCP Tool Reference
All 10 registered tools. Every tool returns a dict — success includes data keys + optional messages/warnings lists; error includes "error": str.
backlog_add
Parameters:
title str required Item title
priority str required "P0" | "P1" | "P2" | "Ideas"
description str required Item description
source str optional Where this item came from (default: "Not specified")
type str optional "Feature"|"Bug"|"Refactor"|"Docs"|"Chore" (default: "Feature")
force bool optional Skip fuzzy duplicate check (default: false)
Returns: {file_path, title, priority, issue?, messages, warnings}
CLI: uv run "${CLAUDE_PLUGIN_ROOT}/sam_schema/cli.py" backlog add --title X --priority P1 --description D
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.
- 8d ago First seen · 548 lines · 87 tokens per session scan A 16cf977bfd0b
backlog-mcp-validator is an agent published in the GitHub repository Jamie-BitFlight/claude_skills (66 stars, last pushed today), licensed MIT. It adds 87 tokens to every session and 6,404 once invoked, about $0.0004 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-30.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.