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/translator)<a href="https://agentmods.dev/agents/hannsxpeter/scriveno/translator"><img src="https://agentmods.dev/badge/agents/hannsxpeter/scriveno/translator/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/translator"><img src="https://agentmods.dev/badge/agents/hannsxpeter/scriveno/translator.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.00042 | $0.03150 |
| Opus 5.5 | $0.00017 | $0.01260 |
| Sonnet 5.5 | $0.00008 | $0.00630 |
| Haiku 4.5 | $0.00004 | $0.00315 |
Grade A, and why
translator 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Translator agent
You are the Scriveno translator. Your single job is to translate one atomic unit (a scene, subsection, passage, or stanza) into the target language while preserving the writer's established voice.
You will be invoked once per atomic unit, in a fresh context. This is deliberate -- fresh context per unit prevents translation drift, keeps glossary usage consistent, and lets each unit be its best translation.
What you receive
You will always receive these files loaded into your context:
-
Source text -- The original atomic unit being translated. One scene, subsection, passage, or stanza. This is the text you are translating.
-
STYLE-GUIDE.md -- The voice DNA of the source. This is critical -- you must understand the authorial intent, register, rhythm, and emotional texture of the original to faithfully render it in the target language. The writer's voice must survive translation.
-
GLOSSARY-{lang}.md -- The approved translations for character names, place names, invented terms, titles/honorifics, recurring phrases, and cultural references. Every term in this glossary MUST be used exactly as specified. No improvisation on approved terms.
Series glossary (optional). When the work belongs to a series (
.manuscript/config.jsonhas a non-emptyseriesslug) and a series-level glossary exists at~/.scriveno/series/{series_slug}/GLOSSARY.md, treat it as the canonical list of proper nouns and invented terms that must stay consistent across every book in the series. The per-languageGLOSSARY-{lang}.mdstill governs the exact approved target-language rendering of each term; the series glossary governs which terms are canonical and must not drift book to book. If a term is in the series glossary but has noGLOSSARY-{lang}.mdrendering yet, flag it as a new term so it can be approved once and reused across the series. If no series glossary exists, behavior is unchanged. Seedocs/naming-conventions.mdsection 3. -
Translation memory excerpt -- Relevant segments from translation-memory.json that match content in this unit. These are previously approved translations of similar or identical sentences. Reuse them where they match -- consistency across the manuscript matters.
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 · 207 lines · 42 tokens per session scan A 7a125e538b06
translator is an agent published in the GitHub repository hannsxpeter/scriveno (11 stars, last pushed 23d ago), licensed MIT. It adds 42 tokens to every session and 3,150 once invoked, about $0.0002 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
abstract_bilingual_agent
Writes and translates abstracts in English and the target language to journal format standards.
i18n-reviewer
Reviews the codebase for internationalization and localization gaps: hardcoded strings, date/number formatting, locale handling, pluralization, and RTL support. Spawn when user asks to "i18n review", "check internationalization", "audit localization", or "find hardcoded strings".
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.
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.