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 skills/stellarshenson/claude-code-plugins/apply-footnotesnpx skills add stellarshenson/claude-code-plugins --skill apply-footnotesgit clone --depth 1 https://github.com/stellarshenson/claude-code-pluginsWrote 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/stellarshenson/claude-code-plugins/apply-footnotes)<a href="https://agentmods.dev/skills/stellarshenson/claude-code-plugins/apply-footnotes"><img src="https://agentmods.dev/badge/skills/stellarshenson/claude-code-plugins/apply-footnotes.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.00021 | $0.00458 |
| Opus 5 | $0.00010 | $0.00229 |
| Sonnet 5 | $0.00004 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
apply-footnotes 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.
What it actually says
Apply Footnotes
Read the datascience:footnotes skill first - it is the single source of truth for the footnote pattern. Do NOT duplicate its content here.
Add Jupyter-compatible footnotes to a notebook or markdown file. Converts inline references to superscript anchor links with a footnote section.
What to do
-
Read the target file
-
Identify what needs footnotes based on user's request:
- Paper references mentioned in prose
- Technical claims that need sources
- Acronyms or terms that need definition
- Data sources that need attribution
- User-specified items
-
For each footnote:
- Insert
[<sup>N</sup>](#fnN)at the reference point in text - Add
- <span id="fnN">N Footnote content.</span>as a bullet in the footnote section - no<sup>inside the target, no<br>; bullets space themselves
- Insert
-
If no footnote section exists, create one:
- In notebooks: add
## Footnotesmarkdown cell at the end, or---separator in the same cell - In markdown: add
---separator + footnotes at the bottom
- In notebooks: add
-
Number footnotes sequentially: fn1, fn2, fn3...
- If file already has footnotes, continue from the highest existing number
Fixing existing footnotes
If the file has broken footnotes:
- Missing
idon spans -> add them - Mismatched numbers (sup says 3 but id says fn5) -> renumber
- Plain
[1]references -> convert to[<sup>1</sup>](#fn1)pattern - Footnotes separated by
<br>or bare lines -> one bullet per footnote, no<br> - Standard markdown
[^1]syntax (not supported in Jupyter) -> convert to anchor pattern
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.
- 3d ago First seen · 42 lines · 21 tokens per session scan A f21952d8ad7c
apply-footnotes is a skill published in the GitHub repository stellarshenson/claude-code-plugins (3 stars, last pushed 4d ago), licensed MIT. It adds 21 tokens to every session and 458 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-31.
Other skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
read
Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask in any language to read, fetch, check, summarize, quote, cite, convert, or save a URL or PDF. Not for local…
docx-comment-reply
Reply to comments (批注) in Word .docx/.doc files: extract comment context, draft replies, write threaded replies back, and validate OOXML.