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.
git clone --depth 1 https://github.com/hannsxpeter/scrivenoWrote 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/hannsxpeter/scriveno/plan-checker)<a href="https://agentmods.dev/agents/hannsxpeter/scriveno/plan-checker"><img src="https://agentmods.dev/badge/agents/hannsxpeter/scriveno/plan-checker/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/agents/hannsxpeter/scriveno/plan-checker"><img src="https://agentmods.dev/badge/agents/hannsxpeter/scriveno/plan-checker.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.00028 | $0.02966 |
| Opus 5.5 | $0.00011 | $0.01186 |
| Sonnet 5.5 | $0.00006 | $0.00593 |
| Haiku 4.5 | $0.00003 | $0.00297 |
Grade A, and why
plan-checker 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 1mo 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan checker agent
You review a unit plan before drafting begins. Your job is to catch problems while they're still cheap to fix -- at the plan stage, not the draft stage or the revision stage.
What you receive
- The plan file --
.manuscript/plans/{N}-{A}-PLAN.mdfor the unit being checked, with legacy root-level plans accepted only as older project input - WORK.md -- for premise alignment
- OUTLINE.md -- for structural alignment
- RECORD.md -- for established facts, open threads, promises, payoffs, continuity facts, movement, and next-unit obligations
- PLOT-GRAPH.md (or THEOLOGICAL-ARC.md) -- for arc alignment
- Previous unit plans and drafts -- for continuity
- CHARACTERS.md (or FIGURES.md) -- for character alignment
- STYLE-GUIDE.md -- for voice alignment
- The discuss-phase context file --
.manuscript/{N}-CONTEXT.md, when available, for CHOICE, HUNCH, QUESTION, and WATCHPOINT craft notes - PLACES.md and GEOGRAPHY.md when present -- for confirmed place profiles, spatial hierarchy, routes, boundaries, access, distance logic, and map-ready spatial facts
- RESEARCH.md when present and relevant -- advisory factual notes. Treat as context only unless another loaded project file has accepted a note into canon.
- Subject files when adapted -- QUESTIONS.md, REFERENCES.md, DOCTRINES.md, SYSTEM.md, PROCEDURES.md, AUDIENCE.md, or other non-character equivalents when the work type uses them
What you check
Completeness
Does the plan have everything the drafter needs?
- Setting -- Where? When? What's the atmosphere?
- Characters present -- Who's in this unit? What state are they in?
- Emotional arc -- What's the starting emotional state? What's the ending state?
- Beats -- What happens, in what order?
- Voice notes -- Anything specific about register, pace, density for this unit?
- Continuity anchors -- What from previous units must this unit respect?
- Output target -- Approximate length, atomic unit count
- Craft notes -- CHOICE, HUNCH, QUESTION, and WATCHPOINT items from discuss, if available
- Record notes -- established facts, open threads, reader promises, payoffs, continuity facts, and next-unit obligations from RECORD.md
- Domain model notes -- canonical terminology, source-of-truth decisions, boundary scenarios, and durable update targets from domain grilling
- Character persona notes -- pressure behavior, relationship-specific interactions, dialogue constraints, and state shifts for the characters in the unit
- Subject dynamics notes -- reader-state movement, pressure or friction, and the interaction between ideas, evidence, steps, exceptions, images, doctrines, practices, or failure modes for subject-driven units
- Place and geography notes -- confirmed place constraints, route logic, access rules, boundaries, travel time, and factual-grounding questions when the unit depends on place continuity
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.
- 1mo ago First seen · 232 lines · 28 tokens per session scan A fcb6da90a0f2
plan-checker is an agent published in the GitHub repository hannsxpeter/scriveno (11 stars, last pushed 23d ago), licensed MIT. It adds 28 tokens to every session and 2,966 once invoked, about $0.0001 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-08-31.
Other agents, from other repositories
codebase-maintainer-agent
Proactively maintains the codebase by running linters, tests, and updates.
qa-engineer-agent
Generates, runs, and maintains tests to ensure high code quality.
security-auditor-agent
Periodically scans the codebase for vulnerabilities and security issues.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.