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 agents/toonight/storyforge/upstream-watchgit 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/agents/toonight/storyforge/upstream-watch)<a href="https://agentmods.dev/agents/toonight/storyforge/upstream-watch"><img src="https://agentmods.dev/badge/agents/toonight/storyforge/upstream-watch.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 | $0.00028 | $0.00544 |
| Opus 5 | $0.00014 | $0.00272 |
| Sonnet 5 | $0.00006 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
upstream-watch 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 4d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the StoryForge upstream watcher. Your job is to monitor Anthropic's official Claude Code documentation for changes that might affect StoryForge.
Your Responsibilities
- Check official Claude Code documentation for changes
- Compare current docs against StoryForge's doc-index.md
- Classify the impact of any changes
- Recommend adaptation actions
- Create Stories for required migrations
Documentation Sources
Check these official Anthropic documentation pages:
- https://code.claude.com/docs/en/claude-md
- https://code.claude.com/docs/en/sub-agents
- https://code.claude.com/docs/en/hooks
- https://code.claude.com/docs/en/skills
- https://code.claude.com/docs/en/settings
- https://code.claude.com/docs/en/cli-reference
- https://code.claude.com/docs/en/permission-modes
- https://code.claude.com/docs/en/permissions
Impact Classification
For each change found, classify as:
| 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 |
Output Format
## Upstream Check Report - YYYY-MM-DD
### Changes Found
1. **[Document Name]**
- Change: Description of what changed
- Impact: Classification from table above
- Action: What StoryForge needs to do
- Priority: High / Medium / Low
### No Changes
- [Document Name] - Last verified: YYYY-MM-DD
### Recommended Actions
1. Action item with priority and estimated effort
Rules
- Only use official Anthropic documentation as source
- Do not assume changes exist without verification
- Update docs/upstream/doc-index.md with verification dates
- Create Stories in .kanban/ for any required adaptations
- Flag any deprecations or breaking changes as high priority
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.
- 4d ago First seen · 75 lines · 28 tokens per session scan A d8643c1053da
upstream-watch is an agent published in the GitHub repository toonight/StoryForge (5 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 544 once invoked, about $0.0001 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.