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/story)<a href="https://agentmods.dev/commands/tattooinmtl/blendermcp_dominator/story"><img src="https://agentmods.dev/badge/commands/tattooinmtl/blendermcp_dominator/story/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/story"><img src="https://agentmods.dev/badge/commands/tattooinmtl/blendermcp_dominator/story.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.00008 | $0.00514 |
| Opus 5.5 | $0.00003 | $0.00206 |
| Sonnet 5.5 | $0.00002 | $0.00103 |
| Haiku 4.5 | $0.00001 | $0.00051 |
Grade A, and why
story 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 2mo 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
Story Workflow
Work with story files for implementation and testing.
Arguments
$ARGUMENTS
Mode Detection
- If argument is "create" or "new" -> Create a new story
- If argument matches existing story -> Implement that story
- Otherwise -> Search for matching story
Create New Story
Step 1: Gather Requirements
Ask user for:
- Feature name
- Brief description
- Key acceptance criteria
Step 2: Create Story File
Create docs/planning/stories/<feature-name>.story.md:
# <Feature Name>
## Overview
<Brief description of the feature>
## User Stories
- As a player, I want to <action> so that <benefit>
## Acceptance Criteria
### AC1: <Criterion Name>
- Given <precondition>
- When <action>
- Then <expected result>
### AC2: <Criterion Name>
- Given <precondition>
- When <action>
- Then <expected result>
## Technical Notes
### Client
- <Phaser scenes/entities affected>
- <UI components needed>
### Server
- <Colyseus room changes>
- <MongoDB schema changes>
- <Validation requirements>
### Anti-Cheat
- <What server must validate>
- <What client cannot be trusted with>
## Out of Scope
- <What this feature does NOT include>
Implement Existing Story
Step 1: Load Story
Read the story file from docs/planning/stories/
Step 2: Review Acceptance Criteria
List all ACs and their status:
- AC1: ...
- AC2: ...
Step 3: Implement
For each AC:
- Write failing test
- Implement the feature (client and/or server)
- Verify test passes
- Mark AC as done
Step 4: Update Story
Mark completed ACs in the story file.
Story Files Location
docs/planning/stories/
├── base-building.story.md
├── resource-system.story.md
├── combat-system.story.md
└── ...
Related Tests
client/__tests__/
server/__tests__/
shared/__tests__/
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.
- 2mo ago First seen · 117 lines · 8 tokens per session scan A 776b1545ed74
story is a command published in the GitHub repository tattooinmtl/BlenderMCP_Dominator (1 stars, last pushed 2mo ago), licensed MIT. It adds 8 tokens to every session and 514 once invoked, about $0.0000 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-08-31.
story compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| storytattooinmtl/BlenderMCP_Dominator | Command | 1 | 2mo ago | MIT | A | 8 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |