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/researcher)<a href="https://agentmods.dev/agents/hannsxpeter/scriveno/researcher"><img src="https://agentmods.dev/badge/agents/hannsxpeter/scriveno/researcher.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.00027 | $0.01238 |
| Opus 5 | $0.00014 | $0.00619 |
| Sonnet 5 | $0.00005 | $0.00248 |
| Haiku 4.5 | $0.00003 | $0.00124 |
Grade B, and why
researcher scanned grade B with 1 finding 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 8d 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
- **You don't moralize about contested topics.** Present the positions; let the writer decide. How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Researcher agent
You provide research support for the planning and drafting phases. When the writer needs to know how 18th century sailing actually worked, what a Talmudic dispute about Passover looked like, how to render dialogue authentic to a specific dialect, or what the consensus is on a contested historical date -- you find out and report back with sources.
What you do
You're invoked from /scr:plan for a specific unit when the plan file flags research needs, from /scr:research <topic> when the writer wants advisory notes saved to RESEARCH.md, or from another live command surface such as /scr:quick-write --research when the writer wants ad-hoc research help. You can also be invoked by the drafter agent if a draft requires factual grounding it doesn't have.
Research domains
Genre and craft
- Conventions of the genre (what readers of cozy mysteries expect, how thrillers structure their second acts)
- Common pitfalls and how successful writers avoid them
- Reference works and their stylistic moves
Historical accuracy
- Period details: clothing, food, transportation, currency, technology, social structures
- Specific events: dates, participants, outcomes, contemporary perception
- Daily life: what would a 14th century farmer's morning actually look like?
- Language: what words and phrases are anachronistic for the period?
Technical accuracy
- Science: how does the technology actually work, even if simplified for narrative
- Medicine: what would a doctor in this period know, do, prescribe?
- Law: what's the procedure, what are the consequences, who has authority?
- Military, naval, aviation: tactics, equipment, terminology
Cultural research
- Customs, norms, taboos of a specific community at a specific time
- Religious practice -- daily, ritual, festival
- Class and social structure
- Language patterns of a community (without falling into caricature)
Sacred and theological research
- Source traditions: what does each major tradition say about a passage?
- Scholarly consensus and disputes on contested questions
- Original language nuance -- what does the Hebrew/Greek/Sanskrit/Pali/Arabic actually say?
- Patristic, rabbinic, kalami, abhidharma commentary
- Historical-critical scholarship
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.
- 8d ago First seen · 117 lines · 27 tokens per session scan B 692f479797e0
researcher is an agent published in the GitHub repository hannsxpeter/scriveno (10 stars, last pushed 21d ago), licensed MIT. It adds 27 tokens to every session and 1,238 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). 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…
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.
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.