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 commands/hundia/autospec/update-backloggit 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/commands/hundia/autospec/update-backlog)<a href="https://agentmods.dev/commands/hundia/autospec/update-backlog"><img src="https://agentmods.dev/badge/commands/hundia/autospec/update-backlog.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.00000 | $0.00800 |
| Opus 5 | $0.00000 | $0.00400 |
| Sonnet 5 | $0.00000 | $0.00160 |
| Haiku 4.5 | $0.00000 | $0.00080 |
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 3d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Backlog
Modify ticket statuses, add tickets, report bugs, or link documentation.
Usage
/update-backlog [action] [details]
Actions
| Action | Syntax | Example |
|---|---|---|
status |
status [ticket] [new_status] |
/update-backlog status 4.3 done |
add |
add [sprint] [description] [owner] [model] |
/update-backlog add 4 "Add caching" Backend sonnet |
bug |
bug [description] |
/update-backlog bug "Login fails on Safari" |
note |
note [ticket] [text] |
/update-backlog note 4.3 "Needs API key" |
docs |
docs [ticket] [doc_paths] |
/update-backlog docs 4.3 docs/api/reference.md |
Status Shortcuts
| Input | Status |
|---|---|
todo, t |
🔲 Todo |
progress, wip, p |
🔄 In Progress |
qa, review, r |
🧪 QA Review |
done, d |
✅ Done |
blocked, b |
⏸️ Blocked |
Instructions
When this command is invoked:
-
Parse the action and details
-
Read current backlog:
- Read
specs/backlog.md - Find the relevant sprint/ticket
- Read
-
Execute the action:
Status Update
- Find the ticket in the backlog
- Change the status emoji
- Add timestamp comment if significant
Add Ticket
- Find the target sprint
- Add new row to ticket table
- Assign next ticket number
- Include model recommendation (haiku/sonnet/opus) based on complexity
Bug Report
- Create bug ticket in Bug Backlog section
- Format:
B.XXfor bug tickets - Reference relevant
docs/section if applicable - Include severity (Critical/High/Medium/Low)
Add Note
- Find the ticket
- Add note as blockquote below ticket table
Link Documentation
- Find the ticket in the backlog
- Add docs references to the ticket's Docs column
- Verify the referenced doc files exist
-
Save the backlog:
- Write updated content to
specs/backlog.md
- Write updated content to
-
Confirm the change:
- Show what was changed
- Show new ticket state
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.
- 3d ago First seen · 117 lines · 0 tokens per session scan A ebbf9f79a994
update-backlog is a command published in the GitHub repository Hundia/autospec (4 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 800 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-08-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.