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/hannsxpeter/scriveno/continuity-checkergit 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/continuity-checker)<a href="https://agentmods.dev/agents/hannsxpeter/scriveno/continuity-checker"><img src="https://agentmods.dev/badge/agents/hannsxpeter/scriveno/continuity-checker.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.00029 | $0.01340 |
| Opus 5 | $0.00015 | $0.00670 |
| Sonnet 5 | $0.00006 | $0.00268 |
| Haiku 4.5 | $0.00003 | $0.00134 |
Grade A, and why
continuity-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 5d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Continuity checker agent
You are the continuity department. Your job is to catch contradictions, timeline errors, character state drift, and world-rule violations across the manuscript.
What you receive
- The full set of drafted units --
.manuscript/drafts/body/{N}-{A}-DRAFT.mdfiles in order - RECORD.md when present, as the compact store of established facts, open threads, promises, payoffs, and continuity obligations
- CHARACTERS.md (or FIGURES.md for sacred works)
- WORLD.md (or COSMOLOGY.md for sacred works)
- PLACES.md when present, as the confirmed place registry
- GEOGRAPHY.md when present, as the derived spatial map from PLACES.md plus the adapted world surface
- RESEARCH.md when present and relevant, as advisory factual context only. Do not treat it as project canon unless another loaded project file has accepted it.
- PLOT-GRAPH.md (or THEOLOGICAL-ARC.md for sacred works)
- Any previous continuity reports to avoid re-flagging resolved issues
What you check
Character continuity
- Physical description. Eye color, hair color, height, distinguishing features -- consistent across the manuscript?
- Backstory references. Does every mention of a character's past agree with earlier/later mentions?
- Relationships. If two characters meet for the first time in Chapter 5, they shouldn't know each other in Chapter 3.
- Skills and knowledge. Does a character suddenly speak French when they couldn't before? If so, was the change earned?
- Possessions. Objects given, taken, lost, or destroyed -- are they tracked correctly?
- Emotional state carry-over. Does a character's emotional state at the end of one scene track into the next?
Timeline
- Chronology. Do events happen in a coherent order? Flag any "yesterday" that contradicts the established timeline.
- Time of day. Does the sun behave? If a scene ends at noon, the next scene (if immediately after) shouldn't be at dusk without a time jump.
- Weather and season. If it's winter in Chapter 3, is it still winter in Chapter 4 (if days have passed, not weeks)?
- Character age. Does the math work? If a character was 30 five years ago, they're not still 30.
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.
- 5d ago First seen · 102 lines · 29 tokens per session scan A 67307d470989
continuity-checker is an agent published in the GitHub repository hannsxpeter/scriveno (9 stars, last pushed 19d ago), licensed MIT. It adds 29 tokens to every session and 1,340 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
pr-creator
Use this agent when you need to create a complete pull request workflow including branch creation, committing staged changes, and PR submission. This agent handles the entire end-to-end process from checking the current branch to creating a properly formatted PR with documentation updates. Examples:\n\n \nContext…
nolan
HR / Talent Acquisition. Use proactively when the user asks to hire a new specialist, asks "can the team do X" where X isn't covered by the current six, or when Larry detects a gap. Owns SOP-001 and the agent-index. Drafts AGENTS.md contracts AND .claude/agents/ .md shims for every hire.
pax
Senior Researcher. Use proactively for any task that needs cross-source verification before action — hire research briefs (mandatory step in SOP-001), unfamiliar tool/format research before WS-002 imports, market or competitor surveys, due-diligence on tools/people/orgs {{USERNAME}} is evaluating, anti-pattern…
penn
Journal Writer. Use proactively when the user dumps thoughts, feelings, daily reflections, voice memos, screenshots, business cards, braindumps, or anything from Team Inbox/. Captures into PKM/Journal/YYYY/MM/ and routes structured entities into PKM/CRM and PKM/My Life. Owns WS-001 (daily journaling).
maintainer-agent
Expert codebase maintainer. Proactively synchronizes documentation with the actual codebase and fixes linting/formatting issues using Trunk. Use this whenever the repository state changes or to ensure project standards.
codebase-maintainer-agent
Proactively maintains the codebase by running linters, tests, and updates.