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/configurenpx skills add ondrasek/cc-plugins --skill configuregit 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.00061 | $0.01052 |
| Opus 5 | $0.00030 | $0.00526 |
| Sonnet 5 | $0.00012 | $0.00210 |
| Haiku 4.5 | $0.00006 | $0.00105 |
Grade A, and why
configure 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configure
Generates .github/release.yml for automated release note categorization.
Critical Rules
- Read cross-cutting behaviors first:
skills/shared/references/cross-cutting.md - Always preview the generated config before writing the file
- Validate by generating preview notes after writing the config
- Respect existing configuration — if
.github/release.ymlalready exists, show it and ask before overwriting - Use
--jsonflags for structured output
Prerequisites Check
gh auth status
# Check if release.yml already exists
git ls-files .github/release.yml
cat .github/release.yml 2>/dev/null
If .github/release.yml already exists, show its contents and ask the user whether to update it or create a fresh one.
Capabilities
1. Generate release.yml (Full Workflow)
Step 1: Analyze repo labels
# Get all labels
gh label list --json name,description --limit 200
Group labels by category pattern (e.g., type: *, area: *).
Step 2: Analyze PR history
# Recent PRs with labels
gh pr list --state merged --limit 50 --json title,labels,author
Identify which labels are commonly used on PRs.
Step 3: Generate configuration
Read references/release-yml-guide.md for the full schema and examples.
Map discovered labels to release note categories:
type: feature,enhancement→ "New Features"type: bug,bug,fix→ "Bug Fixes"documentation,docs→ "Documentation"dependencies,dependabot→ "Dependencies"breaking,breaking-change→ "Breaking Changes"
Step 4: Preview config
Show the complete .github/release.yml content to the user. Explain each category and which labels map to it.
Step 5: Write file
After user approval, write .github/release.yml.
Step 6: Validate
# Generate preview notes using the new config
gh api repos/{owner}/{repo}/releases/generate-notes \
-f tag_name="HEAD" \
-f target_commitish="$(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name')" \
--jq '.body' 2>/dev/null
What ships with it
1 file 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 · 146 lines · 61 tokens per session scan A 1d5a44fa3fb2
configure is a skill published in the GitHub repository ondrasek/cc-plugins (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 61 tokens to every session and 1,052 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
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…