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/OKHP3/skillzWrote 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/commands/okhp3/skillz/catalog-skills)<a href="https://agentmods.dev/commands/okhp3/skillz/catalog-skills"><img src="https://agentmods.dev/badge/commands/okhp3/skillz/catalog-skills.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.1 | $0.00000 | $0.00196 |
| Opus 5 | $0.00000 | $0.00098 |
| Sonnet 5 | $0.00000 | $0.00039 |
| Haiku 4.5 | $0.00000 | $0.00020 |
Grade A, and why
catalog-skills 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 7d 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.
What it actually says
Run the okhp3-skill-cataloger to scan .agents/skills/ and regenerate the skills catalog README.
Steps:
- Confirm working directory is the project root (not inside .agents/skills/).
- Find the generator script — prefer
scripts/gen-skills-readme.py, fall back to.agents/skills/okhp3-skill-cataloger/scripts/gen-skills-readme.py. - Run:
python3 {script} --skills-dir .agents/skillsMode is auto-detected. No --mode flag needed unless auto-detection is wrong (see .agents/skills/okhp3-skill-cataloger/references/MODES.md). - Report: number of skills cataloged, detected mode, whether README changed or was already current, any validation warnings, and the updated timestamp shown in the README.
For distribution repos: use /index-skills to catalog root-level family folders into SKILLS.md.
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.
- 7d ago First seen · 11 lines · 0 tokens per session scan A d7a10fe17151
catalog-skills is a command published in the GitHub repository OKHP3/skillz (3 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 196 tokens. 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 commands, from other repositories
drupal
Perform comprehensive Drupal 11 code audit and security analysis.
api-doc
Reads backend route files and generates OpenAPI 3.0 YAML documentation, saved to docs/openapi.yaml. Supports Express, Fastify, Koa, Hapi. Auth middleware is auto-detected.
commit-msg
Reads the current git diff (staged and unstaged changes), analyzes what changed, and suggests a Conventional Commits-compliant commit message.
nxt-api-route
Generates a Next.js App Router API route handler (route.ts) with proper TypeScript types, request validation, and error handling. Auto-detects auth patterns from the project.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.