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 skills add ondrasek/cc-plugins --skill browsegit clone --depth 1 https://github.com/ondrasek/cc-pluginsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/ondrasek/cc-plugins/browse)<a href="https://agentmods.dev/skills/ondrasek/cc-plugins/browse"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/browse/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ondrasek/cc-plugins/browse"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/browse.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00064 | $0.01056 |
| Opus 5.5 | $0.00026 | $0.00422 |
| Sonnet 5.5 | $0.00013 | $0.00211 |
| Haiku 4.5 | $0.00006 | $0.00106 |
Grade A, and why
browse 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 1mo ago.
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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browse
Read-only — does not create or modify releases.
Critical Rules
- Read cross-cutting behaviors first:
skills/shared/references/cross-cutting.md - Always use
--jsonflags for structured data, then present human-readable summaries - Verify
ghis available before running any commands
Prerequisites Check
gh auth status
If this fails, tell the user to run gh auth login first.
Capabilities
1. List Releases
Translate natural language queries into gh release list flags.
Query translation examples:
| User says | Command |
|---|---|
| "show releases" | gh release list --limit 10 --json tagName,name,isDraft,isPrerelease,publishedAt |
| "latest release" | gh release view --json tagName,name,body,publishedAt,assets |
| "show stable releases" | gh release list --exclude-drafts --exclude-pre-releases --json tagName,name,publishedAt |
| "list drafts" | gh release list --json tagName,name,isDraft,publishedAt then filter isDraft=true |
| "releases this year" | gh release list --limit 50 --json tagName,publishedAt then filter by date |
Common flags:
gh release list \
--limit 30 \
--exclude-drafts \
--exclude-pre-releases \
--json tagName,name,isDraft,isPrerelease,publishedAt,isLatest
Output format: Present as a readable table. Include tag, title, date, and status indicators (draft, prerelease, latest). Add relative timestamps (e.g., "3 weeks ago").
2. View Release Detail
Show comprehensive release information.
# Get full release data
gh release view TAG --json tagName,name,body,publishedAt,isDraft,isPrerelease,assets,author,targetCommitish
# Get assets with download counts (if available)
gh release view TAG --json assets
Present:
- Header — tag, title, author, publish date, status (draft/prerelease/latest)
- Release notes — formatted body content
- Assets — file names and sizes
- Target — branch or commit the release was created from
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.
- 1mo ago First seen · 132 lines · 64 tokens per session scan A 104f8252f00e
browse is a skill published in the GitHub repository ondrasek/cc-plugins (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 64 tokens to every session and 1,056 once invoked, about $0.0003 per session on Opus 5.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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Fully automate a release with version-bump and childhood.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.