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/setupnpx skills add ondrasek/cc-plugins --skill setupgit 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.00047 | $0.00869 |
| Opus 5 | $0.00023 | $0.00434 |
| Sonnet 5 | $0.00009 | $0.00174 |
| Haiku 4.5 | $0.00005 | $0.00087 |
Grade B, and why
setup scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat .claude/settings.json 2>/dev/null | jq '.hooks // empty' How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup
Installs a GitHub Actions release workflow and conventional commit validation hook in the target repository.
Critical Rules
- Read references first:
skills/setup/references/conventional-commits.mdandskills/setup/references/workflow-template.md - Never overwrite existing workflows without confirmation — check for
.github/workflows/release.ymlfirst - Verify prerequisites before installing anything
- Present the plan before making changes — user must approve
Prerequisites Check
# Verify tools are available
gh auth status
git rev-parse --is-inside-work-tree
jq --version
If any fail, tell the user what to install before proceeding.
Workflow
Phase 1: Analyze
Gather information about the target repository:
# Existing tags and versioning scheme
git tag --sort=-v:refname | head -10
# Current branch
git symbolic-ref --short HEAD
# Existing CI/CD
ls -la .github/workflows/ 2>/dev/null
# Existing hooks configuration
cat .claude/settings.json 2>/dev/null | jq '.hooks // empty'
ls -la hooks/ 2>/dev/null
Determine:
- Tag prefix convention (default:
v) - Initial version if no tags exist (default:
0.1.0) - Default branch name (main vs master)
- Whether existing release workflows exist
Phase 2: Plan
Present findings to the user:
Detected:
- Tag prefix: v (or none found — will use v)
- Latest tag: v1.2.3 (or none — first release will be v0.1.0)
- Default branch: main
- Existing workflows: [list or none]
Will install:
1. .github/workflows/release.yml — release automation on push to main
2. .github/release.yml — GitHub auto-generated release note categories
3. Conventional commit validation hook (PostToolUse on Bash)
Wait for user approval before proceeding.
Phase 3: Install
-
Create workflow directory:
mkdir -p .github/workflows -
Install release workflow — read
templates/release-workflow.ymlfrom the plugin directory and customize:- Set correct branch name
- Set tag prefix
- Set initial version
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 123 lines · 47 tokens per session scan B 79f8554dea63
setup is a skill published in the GitHub repository ondrasek/cc-plugins (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 47 tokens to every session and 869 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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…