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 skills add toonight/StoryForge --skill story-writegit clone --depth 1 https://github.com/toonight/StoryForgeWrote 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/skills/toonight/storyforge/story-write)<a href="https://agentmods.dev/skills/toonight/storyforge/story-write"><img src="https://agentmods.dev/badge/skills/toonight/storyforge/story-write.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.1 | $0.00038 | $0.00518 |
| Opus 5 | $0.00019 | $0.00259 |
| Sonnet 5 | $0.00008 | $0.00104 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
story-write 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
Story Writer
Create a new StoryForge Story file with all required fields.
Instructions
-
First, read
.kanban/stories/to find the next available Story ID- Count existing STORY-NNN.md files
- Use the next sequential number (e.g., if STORY-003 exists, create STORY-004)
-
Ask the user for:
- Story title (or use $ARGUMENTS if provided)
- Which Feature this belongs to (check
.kanban/features/for existing files and.kanban/board.mdfor the features table) - If the Feature doesn't exist yet, create a new FEAT-NNN.md file in
.kanban/features/using FEAT-TEMPLATE.md as the base, and add it to the Features table in board.md - Which Initiative the Feature belongs to
- Brief context for why this work is needed
- Acceptance criteria (specific, verifiable items)
- Non-goals (what is explicitly out of scope)
-
Create the Story file at
.kanban/stories/STORY-NNN.md:
# STORY-NNN: (Title)
- **Feature**: FEAT-NNN - (Feature Name)
- **Initiative**: INIT-NNN - (Initiative Name)
- **Status**: Backlog
- **Created**: (Today's date)
## Context
(Why this work is needed)
## Acceptance Criteria
- [ ] (Criterion 1)
- [ ] (Criterion 2)
- [ ] (Criterion 3)
## Non-Goals
- (What is explicitly NOT in scope)
## Implementation Notes
(Technical approach or constraints - fill in during planning)
## Validation Notes
(How to verify the work is correct - fill in during planning)
## Risks
- (Known risks or uncertainties)
## Follow-ups
- (Work discovered that should be done later)
- Update
.kanban/board.mdto include the new Story in the Backlog column - Update
.kanban/backlog.mdif a new Feature or Initiative was created - Confirm the Story was created and show its ID
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 · 74 lines · 38 tokens per session scan A 71ce7cf71294
story-write is a skill published in the GitHub repository toonight/StoryForge (5 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 518 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.