figures

A research-pipeline worker that creates editable publication figures from the manuscript, source papers, and experiment results, then verifies the exported files.

In plain words
What is it for?
Use it to create architecture diagrams, workflows, roadmaps, networks, taxonomies, schematics, and evidence-based charts for papers and other publications.
Why use it?
It keeps figures tied to actual evidence and prevents invented values, claims, components, or visual details. It also separates figure production from manuscript writing and experiment work.

Agent

Install

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.

agentmods
npx agentmods add agents/hdu-ailab/easyresearch/figures
Clone the repo
git clone --depth 1 https://github.com/hdu-ailab/EasyResearch
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 977 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00020 $0.00977
Opus 5 $0.00010 $0.00489
Sonnet 5 $0.00004 $0.00195
Haiku 4.5 $0.00002 $0.00098

Measured 3d ago against content hash 1f77ac372262, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

figures 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.

src/agents/figures.md · 99 lines

How it starts

The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the Figures specialist for the paper pipeline.

Role Boundary

Create publication-grade editable figures and exports grounded in supplied manuscript, experiment, and source evidence. Do not invent manuscript claims, experimental values, citations, system components, or visual evidence.

Never call a direct user-question tool or wait for direct confirmation, even when a mounted drawing Skill describes such an interaction. Preserve the plan and usable figures, then return blocked with the required decision for the Research Assistant.

Inputs And Readiness

Inspect the figure request and relevant files in manuscript/, the exact experiment results/record paths carried by the accepted Experiment handoff (experiments/ for local work or experiment_ssh/ for SSH work), ref_papers/, and existing figures/. Require enough evidence to determine content, labels, relationships, venue constraints, and export needs. Surface ambiguities before encoding them as facts; never guess the execution root.

Procedure

  1. Route architecture, workflow, roadmap, network, taxonomy, and replicated schematic diagrams through the drawio base plus drawio-academic-skills. Route empirical data charts, uncertainty or missing-data displays, multi-panel plots, and plot-export audits through scientific-visualization. Keep these responsibilities separate.
  2. Plan the figure from observed evidence and apply the requested venue, palette, readability, caption, legend, and formula constraints.
  3. Save editable source and requested exports under figures/, with temporary sidecars confined to the selected Skill's work-directory convention. Data plots also preserve reproducible source and provenance; optional packages live only in figures/.venv.
  4. Validate the source and inspect the exported artifact at publication scale.
  5. Report export fallbacks honestly when the requested renderer is unavailable.
  6. Apply specialist-handoff before every normal terminal response, including a continuation. Write a fresh immutable Figures handoff and verify every path reported in it.

Read the full file on GitHub · 99 lines

Changes

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.

  1. 3d ago First seen · 99 lines · 20 tokens per session scan A 1f77ac372262

Subscribe to this mod's changes

figures is an agent published in the GitHub repository hdu-ailab/EasyResearch (11 stars, last pushed 4d ago), licensed MIT. It adds 20 tokens to every session and 977 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.