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/browsenpx skills add ondrasek/cc-plugins --skill browsegit 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.00064 | $0.01056 |
| Opus 5 | $0.00032 | $0.00528 |
| Sonnet 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 2d 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.
- 2d 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 4mo 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. 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
release-notes
Draft concise release notes.
greptimedb-release
Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…
store-update
在 CCX Desktop 发布后下载 Store MSIX 并生成发布公告。用户提到 Store 上架、MSIX、从 GitHub Release 下载 store.msix、发布后同步 Windows Store、从 release 填写商店更新内容时必须使用此技能。该技能会下载最新 GitHub Release 的 amd64/arm64 MSIX，校验 sha256，从 Release body 生成 Store listing releaseNotes 预览，并输出手动上传指引。.