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/PinkGranite/EasyPaperWrote 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/commands/pinkgranite/easypaper/easypaper-setup)<a href="https://agentmods.dev/commands/pinkgranite/easypaper/easypaper-setup"><img src="https://agentmods.dev/badge/commands/pinkgranite/easypaper/easypaper-setup/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/commands/pinkgranite/easypaper/easypaper-setup"><img src="https://agentmods.dev/badge/commands/pinkgranite/easypaper/easypaper-setup.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.00000 | $0.00186 |
| Opus 5.5 | $0.00000 | $0.00074 |
| Sonnet 5.5 | $0.00000 | $0.00037 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
easypaper-setup 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.
What it actually says
Set up EasyPaper environment including Python dependencies and LaTeX toolchain.
Execution contract
-
Use the
easypaper-setup-environmentskill to:- Create isolated virtual environment (prefer
uv, fallback tovenv) - Install easypaper package
- Create or validate
easypaper_config.yamlfrom the skill-bundledconfig.example.yamltemplate when the user does not already have config - Check LaTeX installation and provide installation instructions if missing
- Verify all components are working
- Create isolated virtual environment (prefer
-
After setup, provide clear instructions on:
- How to activate the environment
- How to use EasyPaper as Python SDK:
from easypaper import EasyPaper, PaperMetaData - Which config path will be used for generation
- Next steps for using the plugin
$ARGUMENTS
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 · 20 lines · 0 tokens per session scan A 0dcdbd69dea3
easypaper-setup is a command published in the GitHub repository PinkGranite/EasyPaper (5 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 186 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 commands, from other repositories
bib-filter
Filter a LaTeX project's bibliography to the entries actually cited, with Overleaf-source resolution, temporary staging, validation, approval-gated canonical replacement, and compilation. Use before submission or after large revisions.
latex-polish
Inspect a cleanly compiling LaTeX document for source pathologies and rendered visual defects by linting and viewing selected PDF pages. Use when compilation succeeds but title pages, floats, tables, figures, or layout still need publication-quality review. Not for basic compilation health; use $latex-health-check.
latex
Compile one specified LaTeX document, resolve build errors, audit citations, and report build quality. Use when a .tex source must be built or a concrete compilation failure repaired. Not for corpus-wide build checks, visual polish after a clean build, or creating a project; use $latex-health-check, $latex-polish, or…
render-figures
Compile all .tex and .typ figure files in a directory.
autor.paper-writing
Workflow 3: Full paper writing pipeline. Orchestrates paper-plan → paper-figure → paper-write → paper-compile → paper-improver to go from a narrative report to a polished, submission-ready PDF. Use when user says "write paper pipeline", "paper writing", or wants the complete paper generation workflow.
wtfp:export-latex
Export the manuscript and bibliography to portable LaTeX source with declared formatting.