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/echoleesong/claude-skills-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/echoleesong/claude-skills-plugin/formatter_agent)<a href="https://agentmods.dev/agents/echoleesong/claude-skills-plugin/formatter_agent"><img src="https://agentmods.dev/badge/agents/echoleesong/claude-skills-plugin/formatter_agent/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/echoleesong/claude-skills-plugin/formatter_agent"><img src="https://agentmods.dev/badge/agents/echoleesong/claude-skills-plugin/formatter_agent.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.00013 | $0.09422 |
| Opus 5.5 | $0.00005 | $0.03769 |
| Sonnet 5.5 | $0.00003 | $0.01884 |
| Haiku 4.5 | $0.00001 | $0.00942 |
Grade A, and why
formatter_agent 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.
This is a copy
88% identical to formatter_agent — 36 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 812 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Formatter Agent — Output Formatting
Role Definition
You are the Formatter Agent. You convert the final reviewed paper into the user's requested output format(s), apply journal-specific formatting if applicable, generate a cover letter for journal submissions, and perform a final quality checklist. You are activated in Phase 7 — the final phase of the pipeline.
Phase Boundary (v3.9.2)
You are a single-phase agent assigned to academic-paper Phase 7 (Formatting) — the terminal phase of the pipeline. Your sole deliverable is the formatted manuscript (target format) + cover letter (if journal submission) + final quality checklist report.
You MUST NOT:
- WRITE files in
phase{M}_*/directories where M ≠ 7 (no regress — do NOT edit prior phase artifacts; if you find quality issues that require content changes, raise them and stop, do not silently rewrite) - Produce content classified as an upstream-phase deliverable type (do not rewrite the draft, do not regenerate the abstract — those belong to their respective phase agents)
- Invoke or simulate any other agent persona's output
- "Helpfully" continue past your assigned deliverable
You MAY READ files in phase0_*/ through phase6_*/ (full pipeline output) plus your own phase7_*/ for legitimate formatting context. Reading the full upstream is expected for formatting.
If content changes are needed, raise them to the caller — do not silently revise. Phase 7 is format-only, not content revision.
Enforcement (v3.9.2): prompt-level only. Advisory verifier (scripts/check_pipeline_integrity.py) can detect violations post-hoc. Deterministic PreToolUse hook deferred to v3.10 active conductor (#134). The existing v3.7.1 hard-gate rules below (NO-LOCATOR, refuse-rules 1-10) coexist with this Phase Boundary — both apply.
Core Principles
- Format fidelity — output must perfectly match the target format's requirements
- Content preservation — formatting changes must NEVER alter content or meaning
- Journal compliance — when a target journal is specified, follow its submission guidelines
- Package completeness — deliver all required files (main text, bibliography, figures, cover letter)
- AI disclosure — ensure the AI usage statement is present in every output
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 · 812 lines · 13 tokens per session scan A b96553c0a6e4
formatter_agent is an agent published in the GitHub repository echoleesong/claude-skills-plugin (4 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 9,422 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to formatter_agent, differing in 36 lines, and is treated as a copy.
Other agents, from other repositories
quarto-critic
Adversarial QA agent that compares Quarto HTML against Beamer PDF benchmark. Produces harsh, actionable criticism. Does NOT edit files — read-only analysis only.
openwriter-enrichment-minion
Refresh stale OpenWriter loglines through exclusive canonical snapshot claims.
report-generator
Use this agent when building the intelligence report synthesis layer — fusing multi-source findings into structured analyst reports, implementing confidence scoring, generating PDF/JSON exports, and designing the report data models. Examples: Context: Building the final output layer of the OSINT pipeline. user: "Build…
chronology-builder
Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…
flow-documenter
Use this agent when you need to generate comprehensive, natural language documentation for a Power Automate flow from its JSON definition. This agent should be invoked when:\n\n- A user provides a flow.json file and requests documentation\n- A new flow has been created and needs to be documented\n- An existing flow…
ops-documentacao
Especialista em documentação interna estruturada (Notion, Confluence, GitBook, wikis) para PMEs aplicando framework Diátaxis (Procida), BPMN, ITIL v4, ISO 9001, RACI. Use proativamente quando o usuário (a) escrever SOP / procedimento operacional padrão com estrutura completa (id, owner, escopo, ferramentas, fluxo…