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 yuanbw2025/storyforge --skill authoringgit clone --depth 1 https://github.com/yuanbw2025/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/yuanbw2025/storyforge/authoring)<a href="https://agentmods.dev/skills/yuanbw2025/storyforge/authoring"><img src="https://agentmods.dev/badge/skills/yuanbw2025/storyforge/authoring/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/skills/yuanbw2025/storyforge/authoring"><img src="https://agentmods.dev/badge/skills/yuanbw2025/storyforge/authoring.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.00049 | $0.01080 |
| Opus 5.5 | $0.00020 | $0.00432 |
| Sonnet 5.5 | $0.00010 | $0.00216 |
| Haiku 4.5 | $0.00005 | $0.00108 |
Grade A, and why
storyforge-plugin-author 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 15d 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.
How it starts
The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
StoryForge plugin author
Deliver the requested feature as an independent .sfplugin, preserving the user's scope. Explain outcomes and limitations in the user's language. This kit targets the API/SDK recorded in developer-kit.json; it is a reference kit, not a standalone compiler or host.
Locate the matching contract
Read references/PLUGIN-DEVELOPMENT.md and references/index.d.ts for the capabilities relevant to the request. Read guides/develop.md (Chinese) or guides/en/develop.md for environment and CLI setup. The six guides cover capability discovery, installation, AI-assisted development, packaging, publication and recovery. developer-kit.json lists source paths and hashes; compare against the user's host checkout when available. API 1 alone does not imply all preview builds are compatible.
For this skill's source checkout before packaging, use docs/guides/PLUGIN-DEVELOPMENT.md, tools/plugin-sdk/index.d.ts, website-docs/workshop/ and examples/plugins/ at the StoryForge repository root. Do not edit generated kit copies as a second contract.
The public SDK, manifest validator and host implementation decide what is supported. When instructions and types conflict, explain the mismatch and stop the affected part; do not invent signatures, silently switch host versions or patch private host code to claim plugin support.
Map the request before coding
Identify the visible result, work or world owner, UI entry, data, AI/network needs and required public interfaces. Clarify material gaps; make routine UI choices without unnecessary questions. If only part is supported, explain a workable reduced scope and the missing interface.
Choose the nearest example under examples/: writing-notes for data/UI; world-timeline and calendar for replacement/service composition; idea-cards for author-confirmed AI; plot-flow for copied node flows; world-festivals for world adoption; harbor-rules for frozen RulePack; research-desk/tool-desk for network/MCP. For local programs, read references/MCP-BRIDGE.md; construction boundaries are in references/PLUGIN-WORKSHOP-V1.md. Content and bundles have no executable entry. Read only relevant examples.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 15d ago First seen · 43 lines · 49 tokens per session scan A 1398bc1c1325
storyforge-plugin-author is a skill published in the GitHub repository yuanbw2025/storyforge (928 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 1,080 once invoked, about $0.0002 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-10-10.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.