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 skills add adamjali/research-poster-skill --skill research-postergit clone --depth 1 https://github.com/adamjali/research-poster-skillWrote 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/skills/adamjali/research-poster-skill/research-poster)<a href="https://agentmods.dev/skills/adamjali/research-poster-skill/research-poster"><img src="https://agentmods.dev/badge/skills/adamjali/research-poster-skill/research-poster/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/skills/adamjali/research-poster-skill/research-poster"><img src="https://agentmods.dev/badge/skills/adamjali/research-poster-skill/research-poster.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.00198 | $0.04172 |
| Opus 5.5 | $0.00079 | $0.01669 |
| Sonnet 5.5 | $0.00040 | $0.00834 |
| Haiku 4.5 | $0.00020 | $0.00417 |
Grade A, and why
research-poster 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 27d 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<references_contract>
References are mandatory, not optional
This skill ships 6 reference files plus two worked examples in references/examples/. Read the
matching reference BEFORE the step that needs it, never afterwards to check your work.
references/data-integrity.md: reproduce the abstract from the source data (Phase 1)references/venues.md: find and date the venue's rules; institution brand kits (Phases 0 and 2)references/design-rules.md: readability floor, type scale, layout, house style (Phase 3)references/build-and-charts.md: native charts, the repair trigger, python-pptx pitfalls (Phase 4)references/rendering-qa.md: render, readability and overlap checks, QR codes (Phase 5)references/citations.md: verify, format, hyperlink (Phase 2) </references_contract>
This skill encodes a workflow that was hardened in practice. Read the matching reference BEFORE the
step that needs it, not afterwards to check your work (by then the mistake is in the output); do not
reinvent the parts that are already solved (chart-safety, rendering,
typography scale). Scripts live in ${CLAUDE_SKILL_DIR}/scripts/; worked examples and deep guidance
live in ${CLAUDE_SKILL_DIR}/references/. Rendering uses LibreOffice (cross-platform) or Microsoft
PowerPoint on macOS; see references/rendering-qa.md.
<companion_skills> Everything this skill needs is bundled; the build, render, and check run on the scripts here alone. These optional skills add polish. Use any that are installed. If one is missing, carry on without it and mention the one-line install to the user once; never stop for it.
| Skill | Adds | Install (in Claude Code) |
|---|---|---|
Anthropic pptx + pdf (document-skills) |
editing an existing poster, hard PDFs | /plugin marketplace add anthropics/skills, then /plugin install document-skills@anthropic-agent-skills |
frontend-design |
palette, type pairing, layout direction | /plugin install frontend-design@claude-plugins-official |
K-Dense citation-management (MIT) |
PubMed / DOI lookup, formatted references | copy skills/citation-management from github.com/K-Dense-AI/scientific-agent-skills into ~/.claude/skills/ |
K-Dense scientific-visualization (MIT) |
journal-style matplotlib figures (image-chart route) | same repo, skills/scientific-visualization |
Leave out K-Dense pptx-posters (an HTML/CSS poster route that competes for the same requests) and
scientific-writing (manuscript prose that bans the bullets a poster needs). Citation checks need no
extra skill: web search and fetch against PubMed / Crossref / doi.org do the job.
</companion_skills>
<execution_context>
Run interactively OR fully autonomously. Every gate below is an AskUserQuestion with a clearly
marked recommended default, so an autonomous run just takes the defaults and states them.
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/build-and-charts.md 6.5 KB
- references/citations.md 1.8 KB
- references/data-integrity.md 4.5 KB
- references/design-rules.md 5.2 KB
- references/examples/build_poster_example.py 13 KB runs code
- references/examples/make_charts_example.py 4.8 KB runs code
- references/rendering-qa.md 5.7 KB
- references/venues.md 3.7 KB
- scripts/check_charts.py 1.9 KB runs code
- scripts/check_fonts.py 2.2 KB runs code
- scripts/check_overlap.py 1.7 KB runs code
- scripts/qr.swift 2.8 KB
- scripts/render.sh 3.2 KB runs code
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.
- 27d ago Changed · +67 lines 47a7c673c659
- 29d ago Changed · +9 lines · +32 tokens per session af7221e2f231
- 1mo ago First seen · 187 lines · 166 tokens per session scan A 03bb2cd48eb5
research-poster is a skill published in the GitHub repository adamjali/research-poster-skill (2 stars, last pushed 28d ago), licensed MIT. It adds 198 tokens to every session and 4,172 once invoked, about $0.0008 per session on Opus 5.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-31.
Other skills, from other repositories
weekly-load-review
Review weekly training load against the rolling baseline and deliver a coaching summary.
yolo-brief
Use to record a new feature in a YOLO repo, or to cancel one. Writes workspace/features/ /brief.md with a goal and checkable success criteria, taken from an approved design spec when one exists. Triggers on "track this as a feature", "write a brief for X", "track it from that spec", "yolo brief", "cancel the X…
yolo-next
Use when the user asks what to work on next, what to pick up, or what to prioritize in a YOLO repo. Ranks the backlog from derived status, dependencies, stalled work, open issues and code TODOs, and recommends the top 3 with reasons. Read-only. Triggers on "what next", "what should I work on", "what should I pick up"…
yolo-status
Use when the user asks where things stand, what's in progress, what's landed, or "where was I" in a YOLO repo. Derives every feature's status from git and the briefs; nothing is read from a stored status field.
yolo-verify
Use to check a feature branch against its brief's successcriteria and record the result. Writes verification.md and, on a full pass, commits it with the YOLO-Verified trailer. Triggers on "verify this feature", "does it meet the criteria", "yolo verify".
yolo-init
Use when setting up YOLO in a repo for the first time, or repairing the setup. Creates workspace/features/ and workspace/config.yaml. Triggers on "set up YOLO here", "init yolo", "yolo init".