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 jerseycheese/agent-skills --skill skill-paritygit clone --depth 1 https://github.com/jerseycheese/agent-skillsWrote 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/jerseycheese/agent-skills/skill-parity)<a href="https://agentmods.dev/skills/jerseycheese/agent-skills/skill-parity"><img src="https://agentmods.dev/badge/skills/jerseycheese/agent-skills/skill-parity/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/jerseycheese/agent-skills/skill-parity"><img src="https://agentmods.dev/badge/skills/jerseycheese/agent-skills/skill-parity.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.00103 | $0.02021 |
| Opus 5 | $0.00051 | $0.01010 |
| Sonnet 5 | $0.00021 | $0.00404 |
| Haiku 4.5 | $0.00010 | $0.00202 |
Grade A, and why
skill-parity 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 9d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Parity
Keep skills aligned across Claude Code, Codex, Gemini CLI, and the shared Agent Skills layout. Treat Claude as canon only when the user has made that explicit or recent audit context shows Claude is the cleaned source of truth.
Canonical source: the agent-skills repo (symlink-based, Claude side)
The single source of truth for hand-authored skills is the public repo jerseycheese/agent-skills (cloned at ~/Projects/shared/agent-skills). It's also registered as a Claude Code plugin marketplace (jerseycheese-skills -> plugin workflow-skills), but that plugin is deliberately disabled on this machine — plugin skills always need a /plugin-name:skill-name prefix to invoke (no bare-name resolution, even when unambiguous), and that prefix drifted unpredictably (a shifting git-SHA namespace, since the plugin has no pinned version). Bare /skill-name invocation only works for standalone skills, so:
- Edit a skill once in the repo.
git push(keeps the public marketplace listing current for other users/machines).- On this machine, Claude Code loads it via a real symlink at
~/.claude/skills/<name>->~/Projects/shared/agent-skills/skills/<name>— edits are live immediately, no copy or plugin-update step needed. This is canon now, not a fallback; do not remove these symlinks or re-enable theworkflow-skillsplugin (it would double-register the same skill names). - Codex and Gemini hydrate
~/.agents/skills/from the same repo via the copy/symlink paths below (or thefind-skillsinstaller).
New skills added to the repo need a matching symlink created in ~/.claude/skills/ (ln -s ../../Projects/shared/agent-skills/skills/<name> ~/.claude/skills/<name>) — this doesn't happen automatically. The manual copy/prune/hash steps below still apply when working outside the repo or syncing a one-off.
Research-first rule
Before adding, editing, pruning, or syncing Codex/Gemini skills, verify current official guidance. Do this even if this skill contains advice that seems current.
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.
- 9d ago First seen · 130 lines · 103 tokens per session scan A 830a17a43401
skill-parity is a skill published in the GitHub repository jerseycheese/agent-skills (1 stars, last pushed 8d ago), licensed MIT. It adds 103 tokens to every session and 2,021 once invoked, about $0.0005 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
env-scanner
Scan and audit Gemini CLI, Claude Code, Antigravity, Continue, Windsurf, JetBrains AI, and OpenCode environments. Discovers configurations, audits memory tiers, detects skill extraction state, analyzes behavioral tool chains, checks policy governance (v0.40+), and suggests reusable skills with evidence gating.…
scan
Scan your AI coding tool ecosystem — Gemini CLI, Claude Code, Antigravity (Desktop, CLI, IDE), Continue, Windsurf, JetBrains AI, OpenCode. Produces a maturity score, advisory recommendations, and optionally generates reusable SKILL.md files from your conversation patterns. Use when the user asks to audit their…
chorus-council
Run an LLM council — Claude (correctness), Gemini (edge cases), Cursor (integration), Kilo (maintainability), and you (scope) tackle the same task in parallel. Use when the user wants multiple independent perspectives on a decision, approach, or problem.
chorus-vote
Put a yes/no proposition to five agents and tally YES / NO / ABSTAIN votes when the user wants a quick decision signal.
chorus-parallel-debug
Parallel root-cause hypotheses from multiple agents for a reported bug. Use when the user says "parallel debug", "chorus debug", "multiple hypotheses", or "debug with all agents".
chorus-parallel-review
Parallel code review of the current git diff from multiple agents — Claude (correctness/security), Gemini (edge cases), Cursor (integration), Kilo (maintainability), and you (scope/simplicity). Use when the user says "parallel review", "review with all agents", or "chorus review".