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 agentmods add instructions/wubing2023/paperspine/claude-mdgit clone --depth 1 https://github.com/WUBING2023/PaperSpineWrote 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/instructions/wubing2023/paperspine/claude-md)<a href="https://agentmods.dev/instructions/wubing2023/paperspine/claude-md"><img src="https://agentmods.dev/badge/instructions/wubing2023/paperspine/claude-md.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 | $0.00944 | $0.00944 |
| Opus 5 | $0.00472 | $0.00472 |
| Sonnet 5 | $0.00189 | $0.00189 |
| Haiku 4.5 | $0.00094 | $0.00094 |
Grade A, and why
PaperSpine CLAUDE.md 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 4d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PaperSpine Project Memory (V4)
Project Purpose
PaperSpine is a contribution-first paper and report writing skill for Claude
Code, Codex, OpenClaw, and Hermes CLI. It researches the target scene, confirms
the controlling contribution and motivation with the user, then writes/rewrites/
builds end to end with LaTeX/PDF/Word output. The methodology is enforced by
gates: Contribution-First (confirmed_contribution.md), Results-as-
Validation (results_validation.md), Reviewer-Aware (reviewer_audit.md).
Motivation is still required, but it supports the confirmed contribution.
Version: 4.0.0 (canonical: dist/paperspine_version.json, auto-propagated to
.claude-plugin/plugin.json and marketplace.json by the sync script).
Architecture: ONE skill
V4 collapsed the old 12-skill flat suite into a single paper-spine skill —
an orchestrator with 12-stage routing inside SKILL.md, references/ playbooks
for each stage, and agents/ role cards for parallel sub-agents. There are no
longer separate worker skills.
Single source of truth: src/
src/skill/SKILL.md— orchestrator + command/stage routing tablessrc/skill/references/*.md— per-stage playbooks (intake, research, citation, rewrite, build, humanize, latex, audit, translate, submission, respond, resume, contribution, results-validation, reviewer-audit, scenarios, …)src/skill/agents/*— role cards for fan-out agents (research scene/sota/ exemplar, reviewer method/evidence/writing) +openai.yamlsrc/scripts/*.py— deterministic gate/check scripts (standard library only):sync_local_installs.py,contribution_check.py,results_validation_check.py,reviewer_audit_check.py,progress_check.py,submission_check.py,respond_check.py,citation_verification_en.py,latex_guard.py,humanize_check.py,style_metrics.py, etc.src/adapters/{claude,codex,hermes}— per-host frontmatter/manifest overlays
Generated: dist/ (never hand-edit)
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.
- 4d ago First seen · 76 lines · 944 tokens per session scan A 90148781d847
PaperSpine CLAUDE.md is an instructions file published in the GitHub repository WUBING2023/PaperSpine (5,094 stars, last pushed 6d ago), licensed MIT. It adds 944 tokens to every session, about $0.0047 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.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.