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/shawnclybor/clybor-claude-tooling/plugin-buildernpx skills add shawnclybor/clybor-claude-tooling --skill plugin-buildergit clone --depth 1 https://github.com/shawnclybor/clybor-claude-toolingWrote 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/shawnclybor/clybor-claude-tooling/plugin-builder)<a href="https://agentmods.dev/skills/shawnclybor/clybor-claude-tooling/plugin-builder"><img src="https://agentmods.dev/badge/skills/shawnclybor/clybor-claude-tooling/plugin-builder.svg" alt="Measured on agentmods" 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 | $0.00214 | $0.01587 |
| Opus 5 | $0.00107 | $0.00794 |
| Sonnet 5 | $0.00043 | $0.00317 |
| Haiku 4.5 | $0.00021 | $0.00159 |
Grade B, and why
plugin-builder 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 4d 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
7. **Cowork write-protection.** In a Cowork session, `.claude/` is write-protected. New plugin source goes under the plugin dir (e.g. `plugins/<name>/skills/...` or `cowork/<name>/skills/...`), not under `.claude/skills/ The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 4d ago First seen · 67 lines · 214 tokens per session scan B 83c3785c1fdb
plugin-builder is a skill published in the GitHub repository shawnclybor/clybor-claude-tooling (5 stars, last pushed 17d ago), with no licence file. It adds 214 tokens to every session and 1,587 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
ork-assess
Assess a code change, design, architecture, workflow, or competing options against explicit criteria and evidence. Use when a request asks to assess, rate, compare, identify trade-offs, evaluate readiness, or decide whether an approach is good enough. Do not use for a full pull-request review or to implement a chosen…
ork-brainstorm
Compare plausible implementation, architecture, product, or operational approaches before committing to one. Use when a request asks to brainstorm, think through options, choose an approach, evaluate trade-offs, or resolve significant uncertainty before implementation. Do not use for an already specified mechanical…
ork-explore
Map an unfamiliar codebase, feature, architecture, data flow, or operational path with file-backed evidence. Use when a request asks how a system works, where behavior lives, what changed, which dependencies matter, or for onboarding before a change. Do not use to implement or fix the code.
ork-review-pr
Review a pull request or branch for correctness, regressions, security, operational risk, and missing evidence. Use when a request asks to review a PR, review a diff, find real bugs, assess merge risk, or provide evidence-backed review findings. Do not use for implementation or style-only cleanup.
ork-verify
Verify that existing work is ready to merge, release, or hand off using an explicit evidence contract. Use when a request asks to verify, validate, prove, check readiness, run the relevant tests, or distinguish a claimed result from an observed one. Do not use to write missing tests or fix failures.
ork-implement
Make an approved, scoped change and prove the affected behavior. Use when a request asks to implement, build, add, or land a feature that already has an agreed approach. Do not use to explore, review, or verify existing work, or to choose between approaches.