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 skills add nikolamin/claude-coordinator-kit --skill backlog-disciplinegit clone --depth 1 https://github.com/nikolamin/claude-coordinator-kitWrote 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/skills/nikolamin/claude-coordinator-kit/backlog-discipline)<a href="https://agentmods.dev/skills/nikolamin/claude-coordinator-kit/backlog-discipline"><img src="https://agentmods.dev/badge/skills/nikolamin/claude-coordinator-kit/backlog-discipline/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/nikolamin/claude-coordinator-kit/backlog-discipline"><img src="https://agentmods.dev/badge/skills/nikolamin/claude-coordinator-kit/backlog-discipline.svg" alt="Reviewed on agentmods" width="80" 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.00221 | $0.00510 |
| Opus 5 | $0.00111 | $0.00255 |
| Sonnet 5 | $0.00044 | $0.00102 |
| Haiku 4.5 | $0.00022 | $0.00051 |
Grade A, and why
backlog-discipline 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.
What it actually says
Backlog discipline
docs/plan.md and docs/coordination/STATE.md are the single source of truth for pending work.
Do not use suggestion-chip tools or any side backlog. A follow-up discovered mid-work becomes a
new task in docs/plan.md, or a note on existing work in docs/coordination/STATE.md — never a
separate list only the coordinator remembers. The same applies to signals arriving from outside
the coordinator's own work — crash reports, support tickets, monitor alerts, mid-session founder
messages — per the Intake rule in coordinator-kit:phase-loop's Cross-cutting rules: they become
a plan task or a STATE.md note too, never a side list of their own.
This rule also has to travel with every dispatched agent, not just live in the coordinator's own
head: a subagent that calls a suggestion-chip/spawn-task tool on its own creates a stray chip the
coordinator cannot see or clean up. Restate it explicitly in the brief of any dispatched agent
whose task could plausibly turn up a follow-up worth flagging — see
coordinator-kit:agent-brief-hygiene for where this fits alongside the rest of what a brief must
carry.
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 · 32 lines · 221 tokens per session scan A 365a56e8e4e4
backlog-discipline is a skill published in the GitHub repository nikolamin/claude-coordinator-kit (2 stars, last pushed 6d ago), licensed MIT. It adds 221 tokens to every session and 510 once invoked, about $0.0011 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.