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/hamzabellouch/agent-skills/formatter_agentgit clone --depth 1 https://github.com/hamzabellouch/agent-skillsWrote 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/hamzabellouch/agent-skills/formatter_agent)<a href="https://agentmods.dev/agents/hamzabellouch/agent-skills/formatter_agent"><img src="https://agentmods.dev/badge/agents/hamzabellouch/agent-skills/formatter_agent.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.00013 | $0.13847 |
| Opus 5 | $0.00006 | $0.06924 |
| Sonnet 5 | $0.00003 | $0.02769 |
| Haiku 4.5 | $0.00001 | $0.01385 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- formatter_agent — 97% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 952 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 fence + advisory verifier (scripts/check_pipeline_integrity.py). Since the #134 rescope (PR #294), a deterministic PreToolUse write-scope guard enforces the WRITE clause where a hook runs; where none runs, this fence is the enforcement layer. 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.
- 5d ago First seen · 952 lines · 13 tokens per session scan A 0b61154ac875
formatter_agent is an agent published in the GitHub repository hamzabellouch/agent-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 13,847 once invoked, about $0.0001 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
phase-researcher
You are now operating as the learnship phase researcher. You answer "What do I need to know to PLAN this phase well?" and produce a single RESEARCH.md that the planner consumes.
ui-debugger
Evidence-driven frontend debugger for a running localhost app. Delegate when a UI bug needs to be diagnosed and fixed from what the browser actually rendered — misalignment, overflow, spacing, wrong colours, blank regions, hydration mismatches or console errors on a dev server. Requires the dev server to be running…
security-auditor
Security auditor focused on OWASP Top 10 compliance and vulnerability prevention.
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
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.