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 skills/toonight/storyforge/release-adaptnpx skills add toonight/StoryForge --skill release-adaptgit 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/release-adapt)<a href="https://agentmods.dev/skills/toonight/storyforge/release-adapt"><img src="https://agentmods.dev/badge/skills/toonight/storyforge/release-adapt.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.00035 | $0.00459 |
| Opus 5 | $0.00017 | $0.00230 |
| Sonnet 5 | $0.00007 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
release-adapt 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 6d 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
Release Adaptation
Process an Anthropic Claude Code update and determine its impact on StoryForge.
Instructions
-
Identify the release or change to evaluate:
- If $ARGUMENTS contains a version number or URL, use that
- Otherwise, ask the user what changed
-
Use the
upstream-watchagent to check the relevant documentation pages -
For each change found, classify the impact:
| Impact Level | Meaning | Action Required |
|---|---|---|
| No Impact | Change doesn't affect StoryForge | Update doc-index.md verified date |
| Docs Impact | Documentation needs updating | Update relevant StoryForge docs |
| Config Impact | Settings or configuration affected | Update settings.json templates |
| Agent Impact | Agent behavior or format affected | Update agent definitions |
| Hook Impact | Hook events or format changed | Update hook configurations |
| Skill Impact | Skill format or behavior changed | Update skill definitions |
| Migration Required | Breaking change needs migration | Create migration Story |
- For each impacted area, create a record:
## Upstream Change: (Description)
- Source: (URL or release notes reference)
- Checked: (Today's date)
- Impact: (Classification from table)
- Impacted Files: (List of StoryForge files affected)
- Migration Notes: (What needs to change)
- Validation: (How to verify the adaptation)
- Status: Pending | In Progress | Complete
-
Save the record to
docs/upstream/or updatedocs/upstream/release-watch.md -
If migration is required:
- Create a Story using the
story-writeskill - Link it to an appropriate Feature (or create FEAT for upstream adaptation)
- Add it to the sprint backlog if urgent
- Create a Story using the
-
Update
docs/upstream/doc-index.mdwith new verification dates -
Update
docs/anthropic-source-map.mdif capability classifications changed
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.
- 6d ago First seen · 56 lines · 35 tokens per session scan A 361fa147c72d
release-adapt is a skill published in the GitHub repository toonight/StoryForge (5 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 459 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…