Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/toonight/StoryForgenpx agentmods add skills/toonight/storyforge/upstream-checkWrote 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/upstream-check)<a href="https://agentmods.dev/skills/toonight/storyforge/upstream-check"><img src="https://agentmods.dev/badge/skills/toonight/storyforge/upstream-check.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.00031 | $0.00326 |
| Opus 5 | $0.00015 | $0.00163 |
| Sonnet 5 | $0.00006 | $0.00065 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
upstream-check 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 7d 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
Upstream Documentation Check
Check Anthropic Claude Code documentation for changes that may affect StoryForge.
Instructions
- Run the upstream monitor script:
python scripts/upstream_monitor.py
- If changes are detected:
- Review the changed pages manually
- Classify each change using the impact table from
docs/upstream/release-watch.md - For each impactful change, use
/story-writeto create an adaptation Story - After adapting, update the baseline:
python scripts/upstream_monitor.py --update-baseline
- If generating a full report:
python scripts/upstream_monitor.py --report-path docs/upstream/reports
- Update
docs/upstream/release-watch.mdwith findings - Update
docs/upstream/doc-index.mdverification dates
Impact Classification
| Level | Meaning | Action |
|---|---|---|
| No Impact | Cosmetic or unrelated change | Update baseline only |
| Docs Impact | StoryForge docs need updating | Update docs |
| Config Impact | Settings or configuration affected | Update templates |
| Agent Impact | Agent behavior or format changed | Update agents |
| Hook Impact | Hook events or format changed | Update hooks |
| Skill Impact | Skill format changed | Update skills |
| Migration Required | Breaking change | Create migration Story |
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.
- 7d ago First seen · 49 lines · 31 tokens per session scan A d09399406a9c
upstream-check is a skill published in the GitHub repository toonight/StoryForge (5 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 326 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…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…