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/samibs/skillfoundry/paritynpx skills add samibs/skillfoundry --skill paritygit clone --depth 1 https://github.com/samibs/skillfoundryWhat 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.00013 | $0.01051 |
| Opus 5 | $0.00006 | $0.00526 |
| Sonnet 5 | $0.00003 | $0.00210 |
| Haiku 4.5 | $0.00001 | $0.00105 |
Grade A, and why
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 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/parity — Cross-Platform Skill Parity Detector
Compares skills across Claude, Copilot, Cursor, Codex (OpenAI), and Gemini platforms. Detects missing skills and H1 title drift before they cause user-visible divergence.
Usage
/parity Full parity report across all 5 platforms
/parity --missing List only missing skills per platform
/parity --drift List only drifted (title mismatch) skills
/parity --json Machine-readable JSON output
/parity --skill <name> Check a single skill across all platforms
Instructions
You are the Parity Detector. When invoked, run the cross-platform skill comparison and report gaps.
When invoked with no arguments:
Run bash scripts/parity-check.sh and report results.
When invoked with --missing:
Run bash scripts/parity-check.sh --missing — show only skills absent from one or more platforms.
When invoked with --drift:
Run bash scripts/parity-check.sh --drift — show only skills whose H1 title differs between the Claude reference and another platform (indicates out-of-sync regeneration).
When invoked with --skill <name>:
Run bash scripts/parity-check.sh --skill <name> — check a single skill across all platforms, showing presence and title on each.
When invoked with --json:
Run bash scripts/parity-check.sh --json — output structured JSON for pipeline use.
After reporting gaps, suggest the fix:
- Missing skills →
./scripts/sync-platforms.sh sync --allregenerates all platform files fromagents/ - Single missing skill →
./scripts/sync-platforms.sh sync <agent-name> - Drifted titles → Re-run sync for the drifted agents:
./scripts/sync-platforms.sh sync <agent-name>
What the Parity Check Measures
| Check | Description |
|---|---|
| Presence | Skill exists in .copilot/custom-agents/, .cursor/rules/, .agents/skills/, .gemini/skills/ |
| Title parity | H1 title in each platform file matches .claude/commands/ reference |
| Parity % | present / total_claude_skills × 100 per platform |
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 · 124 lines · 13 tokens per session scan A 081035a61caf
parity is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 1,051 once invoked, about $0.0001 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-30.
Other skills, from other repositories
memorix-orchestrate
Use when a main agent needs Memorix to coordinate explicit subagent work through tasks, handoffs, messages, file locks, or the orchestrate CLI.
ring:dispatching-workflows
Executing a phased plan in rolling waves where each phase runs as one multi-agent workflow harness: the supervisor elaborates the phase into tasks against the real landed code, launches a workflow that implements with TDD and runs mandatory in-harness review plus an adversarial contrarian pass (and researchers when…
ring:fixing-lint
Fixing lint to a clean state: runs the linter, groups reported issues into independent streams, and dispatches one parallel fixer agent per stream (ring:backend-go for Go, ring:general-purpose otherwise), iterating until clean. Use when a codebase has lint errors across multiple files. Skip for a single error (fix…
ring:writing-skills
Writing or editing a Ring skill: SKILL.md structure, frontmatter and Agent-Search-Optimization rules, token-efficiency targets, and bulletproofing (Iron Law, rationalization tables, Red Flags) so discipline-enforcing skills resist excuses. Use when creating or revising a skill. Delegates pressure-testing to…
ring:creating-handoffs
Creating a handoff document that captures session state (completed work, decisions, open items, next steps) and delivering it via Plan Mode so the user gets the native 'clear context and continue implementing' resume option. Use when ending a session, when context grows large, or the user says 'handoff', 'save…
ring:using-ring
Enforcing Ring's orchestrator protocol every conversation: dispatch specialist/Explore agents instead of operating tools directly, honor the >3-file hard gate, and run skill discovery before any task. Use at conversation start, before any task, when a request matches auto-trigger phrases (fix issues, refactor, find…