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/ondrasek/cc-plugins/statusnpx skills add ondrasek/cc-plugins --skill statusgit clone --depth 1 https://github.com/ondrasek/cc-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.00055 | $0.00847 |
| Opus 5 | $0.00028 | $0.00424 |
| Sonnet 5 | $0.00011 | $0.00169 |
| Haiku 4.5 | $0.00006 | $0.00085 |
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.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Status
Read-only analysis of what the next release will look like.
Critical Rules
- Never create tags or releases — this skill is read-only
- Always show non-conventional commits — they won't be categorized properly
- Use
--no-mergesto skip merge commits in analysis
Prerequisites Check
git rev-parse --is-inside-work-tree
Workflow
1. Find Latest Tag
LATEST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
echo "Latest tag: ${LATEST_TAG:-none}"
2. List Commits Since Tag
if [ -n "$LATEST_TAG" ]; then
git log "${LATEST_TAG}..HEAD" --format="%h %s" --no-merges
else
git log --format="%h %s" --no-merges
fi
3. Categorize and Analyze
Parse each commit subject against the conventional commit pattern:
^(feat|fix|docs|style|refactor|perf|test|build|ci|chore|revert)(\(.*\))?!?: .+
Group commits by type:
- Breaking Changes (any type with
!orBREAKING CHANGEfooter) - Features (
feat) - Fixes (
fix) - Other (all other conventional types)
- Non-conventional (commits that don't match the pattern)
4. Calculate Version Bump
Breaking changes → MAJOR (X+1.0.0)
Features → MINOR (x.Y+1.0)
Everything else → PATCH (x.y.Z+1)
Highest wins: MAJOR > MINOR > PATCH
5. Present Report
Release Status
==============
Latest tag: v1.2.3 (released 2024-01-15)
Commits since tag: 8
Next version: v1.3.0 (MINOR bump — new features detected)
Breaking Changes:
(none)
Features:
- abc1234 feat(auth): add OAuth2 login flow
- def5678 feat(api): add bulk delete endpoint
Fixes:
- 111aaaa fix: correct null pointer in user lookup
- 222bbbb fix(ui): resolve dark mode toggle
Other:
- 333cccc docs: update API reference
- 444dddd chore(deps): update dependency versions
- 555eeee refactor(auth): simplify token validation
Non-conventional commits (will not be categorized):
- 666ffff Update README
- 777gggg WIP save progress
Preview release notes:
## Features
- feat(auth): add OAuth2 login flow
- feat(api): add bulk delete endpoint
## Fixes
- fix: correct null pointer in user lookup
- fix(ui): resolve dark mode toggle
## Other Changes
- docs: update API reference
- chore(deps): update dependency versions
- refactor(auth): simplify token validation
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 · 125 lines · 55 tokens per session scan A 66c54f51c023
status is a skill published in the GitHub repository ondrasek/cc-plugins (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 55 tokens to every session and 847 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-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…