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/hyperactdoting/composer-plugin/exportnpx skills add hyperactdoting/composer-plugin --skill exportgit clone --depth 1 https://github.com/hyperactdoting/composer-pluginWhat 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.00084 | $0.00629 |
| Opus 5 | $0.00042 | $0.00315 |
| Sonnet 5 | $0.00017 | $0.00126 |
| Haiku 4.5 | $0.00008 | $0.00063 |
Grade A, and why
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 yesterday.
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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Composer — Export to a local file
composer_export_to_file writes the current room contents to a local
markdown file. There is no merge, no diff, no two-way sync —
Composer is authoritative; whatever's at the path becomes a fresh
snapshot on every export. If a file already exists at the path, the
export will overwrite it. Always confirm with the user first when
that's the case — see step 3 below.
Steps
1. Resolve the room
- If exactly one Composer room is attached this session, use it.
- If multiple are attached, ask: "Which doc — paste the URL or roomId." Stop. Do not guess.
- If none are attached, ask the user to
/composer:join <url>first, then re-run.
2. Resolve the path
- The argument must be an absolute path. If it's relative, ask the user for an absolute one (or resolve it against the current working directory if unambiguous — but confirm before doing so).
- The parent directory must already exist. The MCP will not create directories.
3. Check for an existing file and ask permission before overwriting
Before calling the export tool, check whether anything is at the
target path (use whatever read-only tool your host gives you — ls,
stat, Read, etc.):
-
File does not exist — proceed straight to step 4. No confirmation needed; nothing is at risk.
-
File exists — STOP and ask the user explicitly. Show them the path and the consequence in one short line, e.g.:
{path}already exists. Exporting will overwrite it. Want me to go ahead?Wait for an affirmative answer (yes / sure / go ahead / 👍) before calling the tool. If they say no or pick a different path, follow their lead — do NOT call the tool with the original path.
Do not silently overwrite. The user typing /composer:export <path>
opts them into the export, not into clobbering arbitrary local files
without warning.
4. Call composer_export_to_file
composer_export_to_file({ roomId, path: "<absolute>" })
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.
- yesterday First seen · 68 lines · 84 tokens per session scan A fe58bb82adbf
export is a skill published in the GitHub repository hyperactdoting/composer-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 84 tokens to every session and 629 once invoked, about $0.0004 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
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…