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 jimmc414/claude-code-plugin-marketplace --skill match-stable-pairsgit clone --depth 1 https://github.com/jimmc414/claude-code-plugin-marketplaceWrote 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/jimmc414/claude-code-plugin-marketplace/match-stable-pairs)<a href="https://agentmods.dev/skills/jimmc414/claude-code-plugin-marketplace/match-stable-pairs"><img src="https://agentmods.dev/badge/skills/jimmc414/claude-code-plugin-marketplace/match-stable-pairs/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/jimmc414/claude-code-plugin-marketplace/match-stable-pairs"><img src="https://agentmods.dev/badge/skills/jimmc414/claude-code-plugin-marketplace/match-stable-pairs.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.00032 | $0.00777 |
| Opus 5 | $0.00016 | $0.00388 |
| Sonnet 5 | $0.00006 | $0.00155 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
match-stable-pairs 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 10d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
match-stable-pairs
When to Use
- Hospital-resident matching
- Stable marriage problem
- College admissions
- Job candidate matching
- Any two-sided market with preferences
- When you need a "stable" matching (no pair wants to switch)
When NOT to Use
- One-sided assignment (use Hungarian algorithm)
- Weighted matching optimization (different problem)
- When preferences aren't strict orderings
The Pattern
Gale-Shapley Algorithm: Proposers propose in preference order; acceptors tentatively accept best offer so far.
def stable_matching(proposer_prefs, acceptor_prefs):
"""Find stable matching using Gale-Shapley algorithm.
Returns dict mapping proposers to matched acceptors.
Proposer-optimal: proposers get best partner possible.
"""
n = len(proposer_prefs)
# Track state
unmatched = set(range(n)) # Unmatched proposers
matched = {} # acceptor -> proposer
proposals = [list(prefs) for prefs in proposer_prefs] # Remaining preferences
while unmatched:
proposer = unmatched.pop()
if not proposals[proposer]:
continue # Proposer exhausted all options
acceptor = proposals[proposer].pop(0) # Best remaining choice
if acceptor not in matched:
# Acceptor is free, tentatively accept
matched[acceptor] = proposer
elif acceptor_prefs[acceptor].index(proposer) < \
acceptor_prefs[acceptor].index(matched[acceptor]):
# Acceptor prefers new proposer
unmatched.add(matched[acceptor]) # Old match becomes unmatched
matched[acceptor] = proposer
else:
# Acceptor rejects, proposer tries again
unmatched.add(proposer)
return {p: a for a, p in matched.items()}
Example (from pytudes StableMatching.ipynb)
def stable_matching(P, A):
"""Stable matching with preference arrays.
P[i][j] = proposer i's preference for acceptor j (lower = better)
A[i][j] = acceptor i's preference for proposer j (lower = better)
"""
n = len(P)
ids = range(n)
unmatched = set(ids)
matched = {} # acceptor -> proposer
# Pre-sort: for each proposer, list acceptors by preference
proposals = [sorted(ids, key=lambda a: P[p][a]) for p in ids]
while unmatched:
p = unmatched.pop()
a = proposals[p].pop() # Best remaining acceptor
if a not in matched:
matched[a] = p
elif A[a][p] < A[a][matched[a]]: # a prefers p to current
unmatched.add(matched[a])
matched[a] = p
else:
unmatched.add(p) # Rejected, try again
return {(p, a) for a, p in matched.items()}
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.
- 10d ago First seen · 101 lines · 32 tokens per session scan A 1d75ff69f1c7
match-stable-pairs is a skill published in the GitHub repository jimmc414/claude-code-plugin-marketplace (4 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 777 once invoked, about $0.0002 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
audit-progressive-disclosure
Read-only progressive-disclosure audit for agent-facing instruction markdown. Grades every target against a three-tier load-cost model (always-loaded / invocation-loaded / on-demand) and classifies seven finding shapes in two lanes: split opportunities (oversize vs tier-calibrated Anthropic-prescribed caps…
quiz-me
Post-work comprehension check: after a change is complete, generate a self-contained HTML report of what was done (context, intuition, decisions) with a quiz at the bottom that you answer. Verifying the HUMAN absorbed the work, not the artifact. Non-gating by default; the quizpolicy userConfig tunes offer cadence.…
changelog
Ingest Claude Code changelog entries and integrate them into the current repo. Fetch (read-only display), diff (impact analysis, no edits), status (applied versions), and apply (full integrate pipeline, explicit user intent only). Use when: 'new cc version', 'what changed in claude code', 'apply changelog', a new CC…
reach
Run a Claude Code agent turn on ANOTHER machine in the fleet, over SSH on the tailnet. Every machine signs into its own Claude account, so the peer tools (ListAgents, SendMessage) are same-account and never span machines; SSH plus a headless claude -p is the path that does. Carries: resolving a target host from…
shape
Shape the assistant's output for a reader with ADHD, and anyone who wants action-first, low-friction responses. Lead with the concrete next action, number multi-step work, restate state across turns, cap and rank lists, give concrete time estimates, make wins visible, and cut preamble, recap, and closers. Use when…
generate
Build a source-backed AI industry briefing from official vendor publications, configured RSS feeds, GitHub releases, reputable secondary reporting, and user-supplied URLs. Use when: 'ai briefing', 'ai news', 'what's new in AI', 'catch me up on AI', 'prep for AI meeting', 'AI roundup', or 'generate AI slides'.