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.
git clone --depth 1 https://github.com/Hundia/autospecWrote 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/rules/hundia/autospec/update-backlog)<a href="https://agentmods.dev/rules/hundia/autospec/update-backlog"><img src="https://agentmods.dev/badge/rules/hundia/autospec/update-backlog/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/rules/hundia/autospec/update-backlog"><img src="https://agentmods.dev/badge/rules/hundia/autospec/update-backlog.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.00000 | $0.00643 |
| Opus 5.5 | $0.00000 | $0.00257 |
| Sonnet 5.5 | $0.00000 | $0.00129 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
update-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 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Backlog
Rules for managing specs/backlog.md — the central task tracker for this project.
Actions
1. Status Update
Change a ticket's status emoji. Valid transitions:
| From | To | Meaning |
|---|---|---|
| 🔲 | 🔄 | Starting work |
| 🔄 | 🧪 | Implementation done, entering QA |
| 🧪 | ✅ | QA passed, ticket complete |
| 🔄 | ✅ | Small change, QA inline with implementation |
| 🔄 | ⏸️ | Blocked by dependency or decision |
| ⏸️ | 🔄 | Unblocked, resuming work |
| 🧪 | 🔄 | QA failed, returning to development |
2. Add a Feature Ticket
Format: - 🔲 **X.Y** — Description of the feature
Where:
X= sprint numberY= ticket number within the sprint (sequential)
Example:
- 🔲 **16.4** — Add dark mode toggle to viewer settings panel
3. Add a Bug Ticket
Format: - 🔲 **B.XX** — Bug description
Where XX is a globally sequential bug number.
Example:
- 🔲 **B.23** — Viewer crashes when spec file contains empty YAML frontmatter
Bug tickets should include:
- Steps to reproduce (if known)
- Expected vs actual behavior
- Affected component (CLI, Viewer, etc.)
4. Add a Note
Add context to a ticket using a sub-bullet:
- 🔄 **16.3** — Create Cursor IDE skill files
- Note: Using .mdc format with YAML frontmatter
5. Add Documentation Links
When a ticket produces or updates documentation, link it:
- ✅ **16.3** — Create Cursor IDE skill files
- Docs: `docs/environments/cursor-setup.md`
Formatting Rules
- Preserve existing section headers and sprint boundaries
- Keep tickets in numerical order within each sprint
- Do not remove completed tickets — they serve as history
- Use exactly one space after the status emoji
- Bold the ticket number with
**X.Y** - Use an em dash
—(space-emdash-space) between number and description - Keep descriptions concise (one line, under 80 characters)
Status Summary Shortcuts
When reporting sprint status, count tickets by emoji:
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 · 99 lines · 0 tokens per session scan A aad122726287
update-backlog is a cursor rule published in the GitHub repository Hundia/autospec (4 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 643 tokens. 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 cursor rules, from other repositories
slice-tasks
PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
elite-orchestrator
Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).
sprint-planning
BMAD BMM Agent: sprint-planning.