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/lunartech-x/superpowers/formatter_agentgit clone --depth 1 https://github.com/LUNARTECH-X/superpowersWhat 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 | $0.00013 | $0.07935 |
| Opus 5 | $0.00006 | $0.03967 |
| Sonnet 5 | $0.00003 | $0.01587 |
| Haiku 4.5 | $0.00001 | $0.00793 |
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 2d 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
2 near-identical copies found in the catalogue:
- formatter_agent — 95% identical, 8 lines differ
- formatter_agent — 88% identical, 36 lines differ
How it starts
The opening of the file, as written. The whole thing — 786 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.
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
Supported Output Formats
1. Markdown (.md)
- Default output format
- Clean markdown with proper heading levels
- Reference list at the end
- Tables in markdown format
2. LaTeX (.tex + .bib)
Reference: references/latex_template_reference.md
Main .tex file:
- Document class:
article(default) or journal-specific - Packages:
amsmath,graphicx,hyperref,natbiborbiblatex - Sections mapped to
\section{},\subsection{}, etc. - Tables as
tabularenvironments - Figures as
figureenvironments with captions - Citations as
\cite{},\citep{},\citet{}
Bibliography .bib file:
- All references in BibTeX format
- Entry types:
@article,@book,@inproceedings,@techreport, etc. - DOI field included where available
- Consistent citation keys:
AuthorYearorAuthor_Year_Keyword
3. DOCX (via Pandoc when available)
Preferred behavior:
- If Pandoc is available, generate the
.docxfile directly - If Pandoc is unavailable, provide complete markdown + DOCX conversion instructions
- Include a style mapping guide (Heading 1 = Level 1, etc.)
- Include font/margin/spacing specifications
- Use Pandoc command:
pandoc input.md -o output.docx --reference-doc=template.docx
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.
- 2d ago First seen · 786 lines · 13 tokens per session scan A 9f4c62fa1f73
formatter_agent is an agent published in the GitHub repository LUNARTECH-X/superpowers (16 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 7,935 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-30.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.