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 kanban-bootstrapgit 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/kanban-bootstrap)<a href="https://agentmods.dev/skills/toonight/storyforge/kanban-bootstrap"><img src="https://agentmods.dev/badge/skills/toonight/storyforge/kanban-bootstrap.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.00050 | $0.00561 |
| Opus 5 | $0.00025 | $0.00280 |
| Sonnet 5 | $0.00010 | $0.00112 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
kanban-bootstrap 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
Kanban Bootstrap
Initialize a StoryForge Kanban delivery structure for the current project.
Instructions
Create the following directory structure and files in the current project:
Directory: .kanban/
File: .kanban/board.md
# $ARGUMENTS Kanban Board
## Initiative: INIT-001 - (Define the primary initiative)
### Backlog
(No items yet)
### Ready
(No items yet)
### In Progress
(No items yet)
### Review
(No items yet)
### Done
(No items yet)
---
## Features
| ID | Title | Initiative | Status |
|---|---|---|---|
File: .kanban/backlog.md
# $ARGUMENTS Backlog
## Initiatives
### INIT-001: (Define the primary initiative)
- Status: Backlog
- Goal: (Define the strategic goal)
---
## Backlog Items
(No items yet)
---
## Discovered During Implementation
(Items added here during work on other stories)
File: .kanban/sprint.md
# $ARGUMENTS Sprint
## Current Sprint: (Not yet planned)
- Start: (TBD)
- Goal: (TBD)
### Sprint Backlog
| ID | Title | Status |
|---|---|---|
### Sprint Notes
(No notes yet)
File: .kanban/decisions.md
# $ARGUMENTS Decision Records
(No decisions recorded yet. Use this format:)
## DECISION-NNN: Title
- Date: YYYY-MM-DD
- Status: Proposed | Accepted | Superseded
- Context: Why this decision was needed
- Decision: What was decided
- Consequences: What follows from this decision
- Alternatives considered: What else was evaluated
File: .kanban/changelog.md
# $ARGUMENTS Delivery Changelog
## (Today's date)
- Initialized StoryForge Kanban structure
Directory: .kanban/stories/
Create this empty directory (with a .gitkeep file if needed).
After Creation
- Inform the user that the Kanban structure is ready
- Ask them to define their first Initiative
- Suggest creating their first Feature and Story using the
story-writeskill
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 · 133 lines · 50 tokens per session scan A 24ee55bb6df9
kanban-bootstrap is a skill published in the GitHub repository toonight/StoryForge (5 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 561 once invoked, about $0.0003 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.