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/suggestingnpx skills add hyperactdoting/composer-plugin --skill suggestinggit 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.00076 | $0.02059 |
| Opus 5 | $0.00038 | $0.01030 |
| Sonnet 5 | $0.00015 | $0.00412 |
| Haiku 4.5 | $0.00008 | $0.00206 |
Grade A, and why
suggesting 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Composer suggestions
A suggestion proposes a text replacement: textToFind is the literal
span that gets cut out when the user accepts; replacementText is what
gets inserted in its place. Pending suggestions render as Replace/With
cards in the doc's sidebar. There's no "just edit" — every text change
goes through the user's accept click.
This skill is the full guide for composer_add_suggestion. Load it any
time you're about to call the tool, even on familiar territory — the
failure modes are precise.
Match the span to the request
Before calling composer_add_suggestion, decide what span the user is
actually asking you to change. Three patterns:
1. Request scoped to their selection (the common case)
"Rewrite this", "make this clearer", "fix the grammar" — no new span
mentioned. Pass fromThreadId: <threadId>. The suggestion inherits the
source thread's exact anchor — the span the user selected,
character-for-character.
composer_add_suggestion({
roomId, fromThreadId: event.threadId, replacementText: "…"
})
2. Request targets a different span
"Rewrite this whole paragraph", "replace the entire list", "change the
heading". Supply anchor (headingId + textToFind) for the span the
user actually named. Do not pass fromThreadId — you're no longer
inheriting the thread's span.
3. Proactive suggestion with no source thread
Supply anchor. Keep textToFind tight — do not widen beyond what
you're actually replacing.
Picking a broader textToFind than the user asked for is the main
failure mode. When in doubt, default to path 1.
Cross-span: respond anywhere in the doc
A thread is anchored to one span, but your response isn't confined to it. When the user's question (or your own judgment) points elsewhere:
- Suggest on a different span — call
composer_add_suggestionwith an explicitanchor. You can post multiple suggestions in one turn. E.g. user says "the flour amount is off and so is the bake time" → two suggestions, each anchored to its own span. - Open a new thread elsewhere —
composer_add_commentwith its own anchor. Useful for cross-references ("see also the conclusion") or raising something the user didn't ask about but should see. - Still reply on the original thread too if the user's question deserves a direct answer — but only when the reply says something the suggestion/new-comment doesn't already convey. Don't post "see my suggestion"; the card IS the answer.
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 · 188 lines · 76 tokens per session scan A b77392a5363a
suggesting is a skill published in the GitHub repository hyperactdoting/composer-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 76 tokens to every session and 2,059 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…