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/ne11nn/cantos-plugin/writing-style-analyzergit clone --depth 1 https://github.com/ne11nn/cantos-pluginWrote 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/ne11nn/cantos-plugin/writing-style-analyzer)<a href="https://agentmods.dev/agents/ne11nn/cantos-plugin/writing-style-analyzer"><img src="https://agentmods.dev/badge/agents/ne11nn/cantos-plugin/writing-style-analyzer.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.00000 | $0.00015 |
| Opus 5 | $0.00000 | $0.00008 |
| Sonnet 5 | $0.00000 | $0.00003 |
| Haiku 4.5 | $0.00000 | $0.00002 |
Grade A, and why
writing-style-analyzer 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.
What it actually says
../../.assistants/folio/sub-agents/writing-style-analyzer.md
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 · 1 lines · 0 tokens per session scan A 00daa91d1c7d
writing-style-analyzer is an agent published in the GitHub repository ne11nn/cantos-plugin (1 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 15 tokens. 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
implementer
Implements one sub-task in an isolated git worktree, following TDD where tests exist and Tidy First, then opens a PR ready for review (never a draft). Spawned by the orchestrator with a per-invocation model chosen from the classifier's tier (sonnet for trivial/standard, opus for complex) and an isolated worktree.…
reviewer
Reviews one open PR, posts a consolidated review comment (citing path:line), and emits a verdict of CLEAN or NEEDSFIXES. Rejects PRs that mix structural and behavioral commits. Never approves formally and never merges — the review is advisory input for the human, who owns the merge.
orchestrator
Coordinates the whole pipeline — reads config and task, scopes work across target repos, writes the plan, launches classifier/implementer/reviewer, monitors cycles, and notifies when PRs are ready. Never writes application code. This file specifies the role; the executable step-by-step workflow lives in CLAUDE.md.
classifier
Cheap, fast complexity classifier. Given one sub-task, returns a single complexity tier that decides which model the implementer runs on. Does nothing else — no code, no planning, no side effects.
docs-curator
Documentation drift detection and sync specialist. Use to update docs//.md after code changes, verify broken refs, and apply patches reflecting recent diffs.
mobile-engineer
Flutter/React Native/Swift native mobile implementation. Use for mobile app, widgets, SwiftUI, platform feature work.