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/tattooinmtl/BlenderMCP_DominatorWrote 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/tattooinmtl/blendermcp_dominator/sprint-status)<a href="https://agentmods.dev/commands/tattooinmtl/blendermcp_dominator/sprint-status"><img src="https://agentmods.dev/badge/commands/tattooinmtl/blendermcp_dominator/sprint-status/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/commands/tattooinmtl/blendermcp_dominator/sprint-status"><img src="https://agentmods.dev/badge/commands/tattooinmtl/blendermcp_dominator/sprint-status.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.00011 | $0.00451 |
| Opus 5 | $0.00005 | $0.00226 |
| Sonnet 5 | $0.00002 | $0.00090 |
| Haiku 4.5 | $0.00001 | $0.00045 |
Grade A, and why
sprint-status 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 10d 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
Sprint Status Workflow
Manage sprint tasks and progress.
Command
$ARGUMENTS
statusor empty -> Show current sprint statusnext-> Get next priority taskupdate-> Update sprint filedone <task>-> Mark task as done
Show Status
Read and display docs/planning/sprint.md:
cat docs/planning/sprint.md
Present summary:
- Current phase/goal
- Tasks in progress
- Tasks remaining
- Any blockers
Get Next Task
Option A: Simple (read sprint.md)
Read docs/planning/sprint.md and find the first unchecked task.
Option B: With Gemini Context
gemini "Read docs/planning/sprint.md and docs/architecture.md.
What's the next priority TODO? Give compact instructions:
1. What to do
2. Key requirements
3. Files to touch (client/server/shared)
4. Acceptance criteria
Under 200 words."
Update Sprint
Modify docs/planning/sprint.md:
- Move tasks between sections
- Add new tasks
- Update blockers
Mark Task Done
Edit docs/planning/sprint.md:
- Change
- [ ]to- [x]for the completed task - Move to Done section if appropriate
Sprint File Format
# Current Sprint
## Goal
<Sprint objective - current implementation phase>
## In Progress
- [ ] Task being worked on
## TODO
- [ ] Next task
- [ ] Another task
## Done
- [x] Completed task
## Blockers
- Any blocking issues
## Notes
- Important context
Related Files
docs/planning/sprint.md- Current sprintdocs/planning/backlog.md- Future workdocs/planning/stories/- Detailed story specs
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.
- 10d ago First seen · 97 lines · 11 tokens per session scan A 953794b5fedb
sprint-status is a command published in the GitHub repository tattooinmtl/BlenderMCP_Dominator (0 stars, last pushed 15d ago), licensed MIT. It adds 11 tokens to every session and 451 once invoked, about $0.0001 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 commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.