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 skills/nickcrew/claude-cortex/backlog-mdnpx skills add NickCrew/Claude-Cortex --skill backlog-mdgit clone --depth 1 https://github.com/NickCrew/Claude-CortexWrote 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/nickcrew/claude-cortex/backlog-md)<a href="https://agentmods.dev/skills/nickcrew/claude-cortex/backlog-md"><img src="https://agentmods.dev/badge/skills/nickcrew/claude-cortex/backlog-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.00057 | $0.01007 |
| Opus 5 | $0.00028 | $0.00504 |
| Sonnet 5 | $0.00011 | $0.00201 |
| Haiku 4.5 | $0.00006 | $0.00101 |
Grade A, and why
backlog-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 today.
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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backlog.md Task Tracking for Agents
Task tracking system optimized for agent workflows via Backlog.md CLI.
Three Primary Use Cases
1. Implementer: Deferring Issues During Feature Work
File P2-P4 issues discovered during implementation. Use label remediation for deferred review findings.
- Create with plan: You have implementation context at filing time
- Assign priority: See priority guide
- Add type label (required) + app labels (optional)
2. Reviewer: Audit Findings
Create structured issues from security/audit reviews. Link dependencies and assign to milestones.
- Create with plan: You're creating from audit context
- Link dependencies as needed
- Assign priority: Ask user if uncertain (label
priority-review) - Set milestones
3. Worker: Executing Assigned Tasks
Read task fully, understand all fields, follow acceptance criteria and definition of done.
- Claim task:
backlog task edit 42 -s "In Progress" -a @myself - Read everything: All fields, attached files/URLs, linked documentation
- Complete systematically: AC → Implementation Notes → Final Summary → DoD → Done
Absolute Rules
- CLI only for writes.
backlog task editandbacklog task createonly. Never edit files directly. - Always use
--plainflag when reading:backlog task 42 --plain,backlog task list --plain - Type label required (bug|feature|documentation|refactor|remediation), single value only
- App labels optional, can be multiple: synapse-pingora, signal-horizon-ui, signal-horizon-api, etc.
- Custom labels allowed as agent-useful (priority-review, performance, security, etc.)
Implementation Plans: When Required
| Scenario | Include Plan? | Reason |
|---|---|---|
| Deferred review issues | ✅ YES | You have audit/review context now |
| Reporting found issues | ❌ NO | Implementer will plan when they work it |
| Explicitly asked to plan work | ✅ YES (detailed) | Required per instruction |
| Regular task work | After claiming, before coding | Don't add at creation, add after starting |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 101 lines · 57 tokens per session scan A 28208afc1b14
backlog-md is a skill published in the GitHub repository NickCrew/Claude-Cortex (37 stars, last pushed 2mo ago), licensed MIT. It adds 57 tokens to every session and 1,007 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
to-issues
将 PRD 拆解为 tracer bullet 垂直切片——每个切片贯穿所有层，可独立演示和验证。Use when the user has an approved PRD and needs it broken down into implementable tasks.
project-plan
按功能模块分组创建项目任务清单。Use after project-init to lay out the feature modules and their tasks, or when updating the project scope.
project-init
在 20项目/ 下创建新项目的总览文档和外部链接文档，设定项目阶段为"启动"。Use when the user wants to start a new project in the Obsidian vault.
project-review
基于 CHANGELOG/commit log 更新项目的里程碑总结。Use after completing a key feature, when switching project phases, or when the user wants a progress review.
project-archive
项目完成后知识反哺 10领域，再移入 90归档。Use when a project is completed or superseded.
Archon Manager
Master Archon MCP for strategic project management, task tracking, and knowledge base operations. The strategic layer (WHAT/WHEN) that coordinates with Skills (HOW). Use when managing projects, tracking tasks, querying knowledge bases, or implementing the Archon+Skills two-layer architecture.