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.
git clone --depth 1 https://github.com/Zeekeey-jpeg/LeRoy-HQWrote 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/agents/zeekeey-jpeg/leroy-hq/skill-matcher)<a href="https://agentmods.dev/agents/zeekeey-jpeg/leroy-hq/skill-matcher"><img src="https://agentmods.dev/badge/agents/zeekeey-jpeg/leroy-hq/skill-matcher/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/agents/zeekeey-jpeg/leroy-hq/skill-matcher"><img src="https://agentmods.dev/badge/agents/zeekeey-jpeg/leroy-hq/skill-matcher.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.00059 | $0.00786 |
| Opus 5 | $0.00030 | $0.00393 |
| Sonnet 5 | $0.00012 | $0.00157 |
| Haiku 4.5 | $0.00006 | $0.00079 |
Grade A, and why
skill-matcher 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 11d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the skill-matcher — a fast, single-purpose routing agent.
Your ONLY job: given a user prompt, find the best matching skill or agent from the index and return a JSON routing result.
Input
You receive a single user prompt string. Nothing else.
Step 1: Load the Index
Read ~/.claude/session/skill-index.json.
If the file is missing, return:
{"type": "no_index", "file": null, "agent": null, "confidence": 0.0, "reason": "skill-index.json not found — run build-skill-index.py"}
Step 2: Match
Score each entry against the prompt using this approach:
- Exact word overlap — count words from the prompt (length > 3, lowercased) that appear in
t(title) ortags - Boost — if the prompt contains the entry's filename stem (e.g., "backup" in prompt → +2 to backup-reminder.md)
- Folder context — if the prompt domain matches the entry's folder tag (e.g., "email" → integrations folder entries score higher)
- Agent+skill preference — when an agent+skill entry and a plain skill entry both match equally, prefer agent+skill
Score entries, take the top match.
Step 3: Confidence Band
| Score | Confidence | Action |
|---|---|---|
| ≥ 3 word matches | 0.90 | Route directly |
| 2 word matches | 0.70 | Route directly |
| 1 word match + folder match | 0.60 | Route directly |
| 1 word match only | 0.40 | Low confidence |
| 0 matches | 0.10 | No match |
If top score ties between 2+ entries, reduce confidence by 0.10 and return the top match.
Step 4: Output
Return ONLY valid JSON on a single line. No explanation, no markdown, no extra text.
High confidence (≥ 0.50):
{"type": "skill", "file": "skills/routines/morning.md", "agent": null, "confidence": 0.90, "reason": "title match: Morning Briefing"}
Agent entry:
{"type": "agent", "file": "agents/builder.md", "agent": "builder", "confidence": 0.85, "reason": "tags: build implement code refactor"}
Agent+skill entry:
{"type": "agent+skill", "file": "skills/workflows/git/pr-workflow.md", "agent": "guardian", "confidence": 0.90, "reason": "tags: commit review pr scope"}
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.
- 11d ago First seen · 78 lines · 59 tokens per session scan A cb4ea2adfdd1
skill-matcher is an agent published in the GitHub repository Zeekeey-jpeg/LeRoy-HQ (10 stars, last pushed 18d ago), licensed MIT. It adds 59 tokens to every session and 786 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 agents, from other repositories
sdk-api-documenter
Generate and validate documentation for @a5c-ai/babysitter-sdk CLI commands and exported APIs.
ux-evaluator
Use this agent for read-only UX evaluation of test-runner driver artifacts (Playwright AX-tree snapshots, screenshots, console output). Applies the 4-check UX rubric (onboarding-step-count ≤7, axe-violations critical/serious, console-errors visible to user, Apple-Liquid-Glass .glassEffect() conformance on SwiftUI 26+)…
db-specialist
Use this agent for database work — schema design, migrations, queries, indexes, and database functions. Handles SQL, ORMs, and database architecture decisions. Context: New feature requires database schema changes. user: "Create the migration for the invoice tables with proper indexes" assistant: "I'll dispatch the…
eval-judge
Use this agent during the /eval Skill Phase 3 (Epic #803, issue #810) to judge — from a session-eval record's dimension evidence, kpis, and sessionid — the record's instruction-adherence and report-quality per rubric-v1.md's Judge Dimensions section. Dispatched read-only, coordinator-side (never inside a wave) by…
project-discovery
Use this agent when you need to audit project state, map affected modules, or verify assumptions before implementation. Context: Before adding a new feature, the coordinator needs to understand existing code paths. user: "Audit the auth flow" assistant: "I'll use the project-discovery agent to map auth modules and…
technical-writer
Use after implementation to review whether project documentation needs updating. Reads the diff and compares against existing docs to identify gaps and stale content. Produces a structured report — does not rewrite docs itself. Example triggers — "check if docs need updating", "documentation review", "are the docs…