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/statusnpx skills add emaballarin/ccplugins --skill statusgit 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.00115 | $0.00608 |
| Opus 5 | $0.00057 | $0.00304 |
| Sonnet 5 | $0.00023 | $0.00122 |
| Haiku 4.5 | $0.00012 | $0.00061 |
Grade A, and why
status 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:status — read-only state
Report where the run stands. Change nothing.
Steps
-
Read state:
cat ./.ar/ar.jsonl 2>/dev/null | tail -50; git branch --show-currentNo
ar.jsonlmeans no run in this repo — say so, point at/ar:start, stop. -
Reconstruct from the last config header and its segment's result lines: run count, keep/discard/crash tallies, best-so-far and its commit, plateau streak, elapsed budget. Method in
${CLAUDE_PLUGIN_ROOT}/references/resume-loop.md§1. -
Print the status block:
AR ACTIVE — <goal> direction minimize (val_bpb) baseline 0.981 noise floor 0.004 (±1.0×) best 0.842 @ a1b2c3d (run 7) runs 23 total — 6 keep · 15 discard · 2 crash budget 23/100 runs · 4h12m/8h00m branch ar/reduce-val-bpb-22-07-2026 (from main @ 9f31c07) last 3 r21 discard 0.851 · r22 discard 0.849 · r23 keep 0.842 ✓ plateau 0 consecutive non-improvements -
Flag anything anomalous without acting on it: the checked-out branch differing from
config.branch, aResult: pendingtrailer onHEAD(an iteration interrupted mid-measurement), an exhausted budget, or astoppedsentinel.
Hard rules
- Read-only. No edits, commits, branch switches, reverts, or iterations —
whatever the state looks like. Reporting a problem is the entire job here;
fixing it belongs to
/ar:resume. - State is read from
./.ar/only. - Report the numbers as recorded. Never recompute a metric, and never infer one that was not measured.
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 · 52 lines · 115 tokens per session scan A 27028ed43479
status is a skill published in the GitHub repository emaballarin/ccplugins (3 stars, last pushed 26d ago), licensed MIT. It adds 115 tokens to every session and 608 once invoked, about $0.0006 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…