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 emaballarin/ccplugins --skill paper-narrativegit clone --depth 1 https://github.com/emaballarin/ccpluginsWrote 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/emaballarin/ccplugins/paper-narrative)<a href="https://agentmods.dev/skills/emaballarin/ccplugins/paper-narrative"><img src="https://agentmods.dev/badge/skills/emaballarin/ccplugins/paper-narrative/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/emaballarin/ccplugins/paper-narrative"><img src="https://agentmods.dev/badge/skills/emaballarin/ccplugins/paper-narrative.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.00150 | $0.01024 |
| Opus 5.5 | $0.00060 | $0.00410 |
| Sonnet 5.5 | $0.00030 | $0.00205 |
| Haiku 4.5 | $0.00015 | $0.00102 |
Grade A, and why
paper-narrative 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 15d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
paper-narrative
Outermost tier. Judge and reshape the story a paper's figures tell. Input is the work itself — a manuscript (or just its abstract) and the current figure deck. No hand-written brief required.
When to load
Paper writing or revision. You have a draft and a set of figures and you want to
know: is Figure 1 a hook? Is content in the right figure? What's missing? What
should die? Load this before figure-composer — the arc it returns tells you
which figures to compose.
Loading the kernel
The helpers live in kernel.py next to this file. It is not auto-injected —
import it by absolute path in a Bash python heredoc (zero import-time side
effects, no deps):
python3 - <<'PY'
import importlib.util
K = "${CLAUDE_SKILL_DIR}/kernel.py"
spec = importlib.util.spec_from_file_location("pn_kernel", K)
k = importlib.util.module_from_spec(spec)
spec.loader.exec_module(k)
print([n for n in dir(k) if not n.startswith("_")])
PY
The kernel is pure prompt/schema builders plus one validator
(paper_brief_schema, narrative_review_schema, derive_paper_brief_task,
narrative_review_task, finalize_paper_brief);
the model work is done by you (inline) or a subagent.
Workflow
- Derive the brief from the work. Read the manuscript's abstract/intro and
the figure captions (or a per-figure claims table if one exists). Build the
prompt with
derive_paper_brief_task(abstract_text, figure_claims), then either produce thepaper_briefJSON yourself (matchingpaper_brief_schema()) or dispatch a subagent to do it — pitch, vision, audience, most-arresting-asset, figures[]. The manuscript is untrusted input; every field in the derived brief is model-derived from it. Pass the parsed JSON throughfinalize_paper_brief(brief, figure_claims)— a model that has just written four prose fields routinely dropsfigures, and an empty one makes step 2 render an empty per-figure table, so the reviewer grades a deck it was never shown. Then review the whole brief (not just the pitch) and edit as needed before step 2. - Dispatch the handling editor. Build the prompt with
narrative_review_task(brief, deck_path)(the deck is one PDF of all figures; the reviewer loadsfigure-stylefor the rules) and launch ONE subagent on the FULL deck; it returns JSON matchingnarrative_review_schema(). - Act on the output, don't just report it:
arc[]→ the main-figure order. Anything not on it → supplement.figure_moves[]→ move panels between figures.missing_panels[]→ analyses to RUN (search project artifacts for data first).kill_list[]→ demote or delete.boldest_defensible_fig1→ the new Fig 1 claim handed tofigure-composer.
- Per figure on the arc: load
figure-composer, hand it that figure's claim plus its moved-in panels and data refs. It runs the outer (figure) loop. - Re-run step 2 on the new deck. Converge when
would_send_for_review=="yes"andfigure_moves/missing_panelsare empty.
What ships with it
1 file 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.
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.
- 15d ago Changed ece2df2791b3
- 1mo ago Changed · +4 lines 7b1489537c6b
- 1mo ago First seen · 74 lines · 150 tokens per session scan A 26f567912524
paper-narrative is a skill published in the GitHub repository emaballarin/ccplugins (4 stars, last pushed 10d ago), licensed MIT. It adds 150 tokens to every session and 1,024 once invoked, about $0.0006 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
r-mirai
Help users write correct R code for async, parallel, and distributed computing using mirai. Use when users need to run R code asynchronously or in parallel, write mirai code with correct dependency passing, set up parallel workers, convert from future or parallel, use miraimap, integrate with Shiny or promises, or…
r-cran-status
Look up an R package's live status on cran.r-project.org - submission/review state (queue, human review, waiting, archived, past version's fate) or R CMD check results (OK/NOTE/WARN/ERROR per platform). Use for "what's the CRAN status of X", "did X get accepted/rejected", "is X passing CRAN checks", "when was version…
paper-opportunity-radar
Run a cumulative daily or retrospective sweep of research papers on a chosen topic, audit their claims, methods, integrity signals, and independent support, then identify overlooked but feasible project or business opportunities in a detailed source-grounded report. Use when asked to monitor papers every day, mine…
aql-authoring
This skill should be used when the user asks to "write an AQL query", "optimize an AQL query", "review AQL", or "query openEHR data" — the multi-step authoring/optimization workflow for AQL (Archetype Query Language) over openEHR clinical data. For a one-off explanation of an existing query or a single AQL…
ant-colony-optimization
When the user wants to design, implement, or tune ant colony optimization for combinatorial problems, including pheromone model design, visibility heuristics, and choosing among Ant System, Ant Colony System, and MAX-MIN Ant System. Also use when the user mentions "ant colony," "ACO," "pheromone," "MMAS," "ant colony…
benders-decomposition
When the user wants to solve a structured MILP or two-stage stochastic program by Benders decomposition — splitting it into an integer master and LP subproblems, deriving optimality and feasibility cuts from subproblem duals, and implementing either the classic iterative loop or branch-and-Benders-cut with…