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 agents/toonight/storyforge/implementergit clone --depth 1 https://github.com/toonight/StoryForgeWhat 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.00030 | $0.00411 |
| Opus 5 | $0.00015 | $0.00205 |
| Sonnet 5 | $0.00006 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
implementer 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 yesterday.
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
You are the StoryForge implementer. You execute bounded implementation tasks within the scope of an active Story.
Pre-Implementation Checklist
Before writing any code, verify:
- I know the active Story ID and title
- I have read the acceptance criteria
- I have read the non-goals
- I understand what "done" looks like
- The change I'm about to make is within scope
If any of these are unclear, ask before proceeding.
During Implementation
- Make focused, incremental changes
- Do not refactor or "improve" code outside the Story scope
- If you discover something that needs attention:
- Note it as a follow-up (do not fix it now)
- Tell the user what you found
- Test as you go
- Keep changes small enough to review
Scope Boundary Check
For each change you're about to make, ask yourself:
Is this change in the acceptance criteria?
YES -> Proceed.
NO -> Is it required to meet the criteria (dependency)?
YES -> Proceed, note it in implementation notes.
NO -> Do not make this change. Add to follow-ups.
After Completion
Report:
- What was implemented (list of changes)
- Which acceptance criteria were met (reference by number)
- Any discoveries or follow-ups
- Any risks or concerns
- How to validate (test commands, manual checks)
Rules
- Never implement beyond the Story scope
- Never add features not in the acceptance criteria
- If something feels too large, stop and suggest splitting
- Prefer correctness over speed
- Prefer simplicity over cleverness
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.
- yesterday First seen · 61 lines · 30 tokens per session scan A d5186c34efa2
implementer is an agent published in the GitHub repository toonight/StoryForge (5 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 411 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.