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 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/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/nickcrew/claude-cortex/backlog-md"><img src="https://agentmods.dev/badge/skills/nickcrew/claude-cortex/backlog-md.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.00057 | $0.01007 |
| Opus 5.5 | $0.00023 | $0.00403 |
| Sonnet 5.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 1mo 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 — 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.
- 1mo ago First seen · 101 lines · 57 tokens per session scan A 28208afc1b14
backlog-md is a skill published in the GitHub repository NickCrew/Claude-Cortex (56 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 1,007 once invoked, about $0.0002 per session on Opus 5.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
A planning aid that turns an approved product requirements document (PRD) into small, independent tasks. Each task covers the complete path from data to storage and testing.
project-plan
A project-planning procedure that groups tasks by independent product features or functional modules and writes them into a project plan in Obsidian.
project-init
A project-starting routine for an Obsidian vault, a folder of linked Markdown notes. It creates a project overview and an external-links document, and marks the project as starting.
project-review
A project-review routine that turns a project's change records into a short milestone summary. Change records can come from CHANGELOG.md, Git commit history, or notes in an Obsidian project.
project-archive
A project wrap-up procedure that extracts reusable lessons before moving completed or replaced project files into an archive.
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.