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/AlterLab-IEU/AlterLab-Academic-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/alterlab-ieu/alterlab-academic-skills/formatter_agent)<a href="https://agentmods.dev/agents/alterlab-ieu/alterlab-academic-skills/formatter_agent"><img src="https://agentmods.dev/badge/agents/alterlab-ieu/alterlab-academic-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.00041 | $0.07114 |
| Opus 5 | $0.00020 | $0.03557 |
| Sonnet 5 | $0.00008 | $0.01423 |
| Haiku 4.5 | $0.00004 | $0.00711 |
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 3d 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 — 762 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 (Instructions for Word)
Since direct DOCX generation is not available, provide:
- Complete markdown with DOCX conversion instructions
- Style mapping guide (Heading 1 = Level 1, etc.)
- Font/margin/spacing specifications
- Instructions for Pandoc conversion:
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.
- 3d ago First seen · 762 lines · 41 tokens per session scan A bd9daf758dae
formatter-agent is an agent published in the GitHub repository AlterLab-IEU/AlterLab-Academic-Skills (64 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 7,114 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
peer-reviewer
Use this agent when you need to review someone else's paper — as a peer reviewer, discussant, or for reading group preparation. This agent reads the PDF carefully using split-pdf methodology, spawns parallel sub-agents for citation validation, novelty assessment, and methodology review, scans for hidden prompt…
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.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
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.