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/plan)<a href="https://agentmods.dev/commands/tattooinmtl/blendermcp_dominator/plan"><img src="https://agentmods.dev/badge/commands/tattooinmtl/blendermcp_dominator/plan/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/plan"><img src="https://agentmods.dev/badge/commands/tattooinmtl/blendermcp_dominator/plan.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.00499 |
| Opus 5 | $0.00005 | $0.00249 |
| Sonnet 5 | $0.00002 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
plan 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 8d 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
Plan Feature Workflow
Feature: $ARGUMENTS
Step 1: Call Gemini
gemini "Read docs/architecture.md.
Task: Plan implementation for: $ARGUMENTS
Output EXACTLY this format:
FEATURE_NAME: <kebab-case-name>
SUMMARY: <one line description>
ACCEPTANCE_CRITERIA:
- AC1: <criterion>
- AC2: <criterion>
- AC3: <criterion>
CLIENT_CHANGES:
- <file path>: <what to change>
SERVER_CHANGES:
- <file path>: <what to change>
SHARED_CHANGES:
- <file path>: <what to change>
IMPLEMENTATION_STEPS:
1. <step>
2. <step>
3. <step>
ANTI_CHEAT_CONSIDERATIONS:
- <what server must validate>
TEST_SCENARIOS:
- <test scenario 1>
- <test scenario 2>
Keep under 400 words."
Step 2: Create Story File
Parse Gemini output and create docs/planning/stories/<FEATURE_NAME>.story.md:
# <Feature Title>
## Overview
<SUMMARY from Gemini>
## Acceptance Criteria
<ACCEPTANCE_CRITERIA from Gemini, formatted as checkboxes>
- [ ] AC1: ...
- [ ] AC2: ...
## Technical Notes
### Client Changes
<CLIENT_CHANGES>
### Server Changes
<SERVER_CHANGES>
### Shared Changes
<SHARED_CHANGES>
### Anti-Cheat
<ANTI_CHEAT_CONSIDERATIONS>
## Implementation Steps
<IMPLEMENTATION_STEPS as checkboxes>
- [ ] Step 1
- [ ] Step 2
## Test Scenarios
<TEST_SCENARIOS>
Step 3: Update Sprint
Add to docs/planning/sprint.md under "In Progress":
- [ ] Implement <feature name> (see stories/<feature-name>.story.md)
Step 4: Start Implementation
Proceed with the mandatory workflow:
- Implement first step
- Write tests for it
- Verify with build and test
- Continue to next step
Mark items complete in the story file as you go.
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.
- 8d ago First seen · 106 lines · 11 tokens per session scan A 5da2f309b52a
plan is a command published in the GitHub repository tattooinmtl/BlenderMCP_Dominator (0 stars, last pushed 13d ago), licensed MIT. It adds 11 tokens to every session and 499 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.