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/emaballarin/ccplugins/stopnpx skills add emaballarin/ccplugins --skill stopgit clone --depth 1 https://github.com/emaballarin/ccpluginsWhat 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.00106 | $0.00608 |
| Opus 5 | $0.00053 | $0.00304 |
| Sonnet 5 | $0.00021 | $0.00122 |
| Haiku 4.5 | $0.00011 | $0.00061 |
Grade A, and why
stop 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.
What it actually says
/ar:stop — end the run
Halt cleanly, leaving everything recoverable.
Steps
-
Read state (
cat ./.ar/ar.jsonl | tail -50). Noar.jsonlmeans no run to stop — say so and stop. -
If
HEADcarries aResult: pendingtrailer, an iteration was interrupted mid-measurement. Leave the commit alone, and record it in the sentinel'sreasonso a later/ar:resumere-measures rather than reverting it. -
Append the sentinel — the last line of the file, and what
ar-loop.shgreps for:{ "run": <n>, "status": "stopped", "segment": <s>, "reason": "<why>" } -
Write
./.ar/final_report.md(see the/ar:reportskill for its shape). -
Print the final status block, the best commit, and — as text, not as a command to run — how to get back:
git switch <config.originBranch> # return to where the run started git log --format='%h %s' --grep='"status":"keep"' <config.branch>
Hard rules
- Destroy nothing. No reverts, no branch deletion, no
git clean. Stopping is not discarding: the experiment branch and every kept commit stay exactly as they are, and the operator decides later what to merge or bin. - Do not switch branches. Print the command and leave the experiment branch checked out for inspection.
- Stopping is reversible — a later
/ar:resumeopens a new segment and carries on from the same state. Say so.
Completion status
End with a terminal status token as the last line of your reply — DONE,
DONE_WITH_CONCERNS, BLOCKED, or NEEDS_CONTEXT — per
references/completion-status.md. For /ar:stop, DONE once the
status:stopped sentinel is appended and the report written; NEEDS_CONTEXT if
there is no active run to stop.
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 · 51 lines · 106 tokens per session scan A 12d2438d5f50
stop is a skill published in the GitHub repository emaballarin/ccplugins (3 stars, last pushed 26d ago), licensed MIT. It adds 106 tokens to every session and 608 once invoked, about $0.0005 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…