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/emdashcodes/claude-code-plugins/quill-exportnpx skills add emdashcodes/claude-code-plugins --skill quill-exportgit clone --depth 1 https://github.com/emdashcodes/claude-code-pluginsWhat 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.00054 | $0.00960 |
| Opus 5 | $0.00027 | $0.00480 |
| Sonnet 5 | $0.00011 | $0.00192 |
| Haiku 4.5 | $0.00005 | $0.00096 |
Grade A, and why
quill-export 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 2d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quill Meeting Export
Export local Quill meetings through the bundled scripts/export_meeting.py script.
Resolve the bundled script
Locate the directory containing this SKILL.md, then set SCRIPT to the absolute path of its bundled exporter:
SCRIPT="<absolute-skill-directory>/scripts/export_meeting.py"
Replace <absolute-skill-directory> before running the command. Use the skill path exposed by the current host. Do not assume the skill is under ~/.claude, ~/.codex, or the current working directory; plugin installations may run from a versioned cache.
Check access
Quill stores its database at:
~/Library/Application Support/Quill/quill.db
Before the first export, verify that the database is readable:
test -r "$HOME/Library/Application Support/Quill/quill.db"
If it is missing, confirm that Quill is installed and has created at least one meeting. If macOS or the execution sandbox denies access, explain the exact path that must be allowed. Do not copy the database or change its permissions without the user's approval.
Treat transcripts and meeting notes as private local data. Only expose or save the meeting content the user requested.
List meetings
List recent meetings before exporting when the user has not supplied an exact meeting ID:
python3 "$SCRIPT" list 20
The list is written to stderr and includes the meeting ID, title, date, duration, and type. Use a smaller or larger positive integer when the user specifies a limit.
Export a meeting
Export by exact meeting ID:
python3 "$SCRIPT" export "76490ffc-d751-4a2a-9ef5-df4d3ddce442"
Or export by a case-insensitive title fragment:
python3 "$SCRIPT" export "orchestrator"
If a title fragment matches multiple meetings, show the short match list and ask the user which meeting they mean. Do not guess based only on recency.
The Markdown document is written to stdout. Status and errors are written to stderr, so redirection is safe:
What ships with it
4 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.
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.
- 2d ago First seen · 102 lines · 54 tokens per session scan A 7f1bb160ee2b
quill-export is a skill published in the GitHub repository emdashcodes/claude-code-plugins (13 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 960 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…