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-metadata-build)<a href="https://agentmods.dev/commands/pinkgranite/easypaper/easypaper-metadata-build"><img src="https://agentmods.dev/badge/commands/pinkgranite/easypaper/easypaper-metadata-build.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.00000 | $0.00574 |
| Opus 5 | $0.00000 | $0.00287 |
| Sonnet 5 | $0.00000 | $0.00115 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
easypaper-metadata-build 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 8d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interactively build EasyPaper metadata from a research-materials folder using Claude Code's file-investigation tools. Output is JSON consumable by /easypaper-paper-from-metadata.
Use this command when the user wants Claude to co-author metadata instead of running the SDK one-shot ep.generate_metadata_from_folder(...) pipeline silently.
Execution Contract
- Present the three modes and wait for an explicit choice:
[1] cold— Claude walks the folder alone, no Python SDK call.[2] warm-start(recommended) — callep.generate_metadata_from_folder(materials_root, max_figures=12, max_tables=12, vision_enrich_figures=False)once, then review/edit every field with the user.[3] refine— load an existing metadata JSON, validate it with the inline checks below, then walk the user through fixes and warnings.
- Ask for the corresponding input:
cold/warm-start:materials_root; resolve it and verify it is an existing directory.refine: existing metadata JSON path; verify it exists.
- Ask for optional style/template settings:
style_guide: target venue or style guide.template_path: path to the LaTeX template zip if known. If relative, interpret it relative to the saved metadata file location during generation.
- Hand off to the
easypaper-interactive-metadata-buildskill for the detailed 6-phase workflow. - Save to
<materials_root>/easypaper_metadata.jsonby default and tell the user to run/easypaper-paper-from-metadatanext.
Inline Validation Rules
Before saving, validate the in-memory metadata with public SDK/Pydantic plus explicit checks:
PaperGenerationRequest.model_validate(metadata_dict)succeeds.title,idea_hypothesis,method,data, andexperimentsare non-empty strings.materials_rootis set to a resolved directory for folder-derived metadata.figures[].file_pathandtables[].file_pathare relative POSIX paths undermaterials_root.- Figure ids use the
fig:prefix; table ids use thetab:prefix. - Figure and table counts are within the selected caps.
- Empty
referencesis a warning, not a hard failure.
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.
- 8d ago First seen · 40 lines · 0 tokens per session scan A 5fabdc81783c
easypaper-metadata-build is a command published in the GitHub repository PinkGranite/EasyPaper (5 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 574 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
verify-math
Verify a self-authored mathematical result end to end by routing claims across adversarial review, numerical falsification, symbolic or CAS checks, and Lean, then aggregating one report. Use when a theorem, proposition, conjecture, or paper-wide mathematical argument needs the appropriate combination of verification…
replication-package
Scaffold or audit a social-science replication package at a target directory, and audit the manuscript and its archived research objects against FAIR principles.
diff
Quantitative volume comparison between a CadQuery model and a reference STEP file.
simulation-calibrator
Test and refine simulation accuracy with validation loops, bias detection, and continuous improvement frameworks.
arg-diagram
ARG academic-paper diagram mode — standalone structural & conceptual diagram generation.
graphite-morphology-classify
Classify graphite in a cast-iron micrograph per ASTM A247 / ISO 945-1, quantify nodularity, and read the matrix — the single most diagnostic observation in a cast-iron case.