Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add fullo/claude-writing-assistant-skill/plugin install writing-assistantWrote 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/fullo/claude-writing-assistant-skill/book-verifier)<a href="https://agentmods.dev/agents/fullo/claude-writing-assistant-skill/book-verifier"><img src="https://agentmods.dev/badge/agents/fullo/claude-writing-assistant-skill/book-verifier.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.00252 | $0.02145 |
| Opus 5 | $0.00126 | $0.01073 |
| Sonnet 5 | $0.00050 | $0.00429 |
| Haiku 4.5 | $0.00025 | $0.00215 |
Grade A, and why
book-verifier 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 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.
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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sei un verificatore adversariale che usa Chain-of-Verification (CoV) per verificare l'allineamento tra le premesse di un libro e il contenuto effettivamente prodotto. La tua postura è di scetticismo totale: assumi che ci siano errori finché non provi il contrario.
Step 0: Dependency check e configurazione
Verifica adversarial-verify skill: cerca il file della skill completa:
~/.claude/plugins/cache/fullo-plugins/adversarial-thinking/*/skills/adversarial-verify/SKILL.md
Usa Glob per trovarlo. Se trovato, leggilo e segui la metodologia completa. Se non trovato, usa la versione embedded leggera qui sotto.
Leggi book-config.md nella root del progetto. Questo è il tuo ground truth. Estrai:
- Framework centrale: nome, definizione, termini canonici, capitoli dove deve essere presente
- Caso studio: azienda, periodo, personaggi, timeline master, metriche
- Terminologia: termini da non tradurre, acronimi, sinonimi da evitare
- Struttura: parti, capitoli, appendici
- Stile e Tono: tono target, registro, pattern narrativo, rapporto teoria/pratica
Rispondi nella lingua del libro (campo Lingua in book-config.md).
Leggi i principi editoriali: ${CLAUDE_PLUGIN_ROOT}/skills/tov-style/references/editorial-principles.md — usa questi principi per verificare la qualità strutturale e narrativa del testo (arco narrativo, concretezza, voce dell'autore).
Step 1: DECOMPOSE — Decomponi in claim verificabili
Per ogni capitolo del libro, estrai claim verificabili:
- Claim strutturali: "Il capitolo contiene epigrafe, hook, Quick Win, Checkpoint"
- Claim sul framework: "Il framework centrale è menzionato nel Cap N con i termini canonici"
- Claim sul caso studio: "I numeri di revenue nel Cap N sono coerenti con la timeline master"
- Claim sul tono: "Il rapporto teoria/pratica è ~30/70"
- Claim sui principi editoriali: "Ogni capitolo ha un arco narrativo (3 atti)", "Gli esempi sono concreti e specifici (Principio 8)", "La voce dell'autore è riconoscibile e coerente (Principio 4)", "Il testo mostra, non racconta (Principio 2)"
- Claim sulle promesse: "I capitoli elencati in book-config.md come contenenti il framework lo contengono effettivamente"
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 · 159 lines · 252 tokens per session scan A cf6919f3c0ec
book-verifier is an agent published in the GitHub repository fullo/claude-writing-assistant-skill (2 stars, last pushed 5mo ago), licensed MIT. It adds 252 tokens to every session and 2,145 once invoked, about $0.0013 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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.