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 alyraffauf/hoenn --skill whygit clone --depth 1 https://github.com/alyraffauf/hoennWrote 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/alyraffauf/hoenn/why)<a href="https://agentmods.dev/skills/alyraffauf/hoenn/why"><img src="https://agentmods.dev/badge/skills/alyraffauf/hoenn/why.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.00089 | $0.04601 |
| Opus 5 | $0.00044 | $0.02301 |
| Sonnet 5 | $0.00018 | $0.00920 |
| Haiku 4.5 | $0.00009 | $0.00460 |
Grade A, and why
why 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 yesterday.
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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
What ships with it
14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- default.nix 333 B
- LICENSE 1.0 KB
- references/epistemics.md 7.6 KB
- references/investigator-prompt.md 6.8 KB
- references/source-playbook.md 1.8 KB
- references/sources/code-archaeology.md 3.4 KB
- references/sources/databricks.md 6.8 KB
- references/sources/datadog.md 5.2 KB
- references/sources/incident-postmortem.md 1.9 KB
- references/sources/linear.md 2.9 KB
- references/sources/notion.md 2.8 KB
- references/sources/sentry.md 4.8 KB
- references/sources/slack.md 3.0 KB
- references/synthesizer-prompt.md 7.8 KB
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.
- yesterday First seen · 234 lines · 89 tokens per session scan A ad526e1b24a7
why is a skill published in the GitHub repository alyraffauf/hoenn (232 stars, last pushed today), licensed GPL-3.0. It adds 89 tokens to every session and 4,601 once invoked, about $0.0004 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-09-06.
Other skills, from other repositories
github-issue
Use when the user wants to start work on a GitHub issue, set up a worktree and development environment, plan the implementation, write tests, and create a PR. Triggers: "start issue", "work on #123", "pick up issue 123", "new issue", or /github-issue [ISSUE].
deep-research-team
This skill should be used when the user asks for "deep research", "research team", "comprehensive analysis", "research report", "investigate thoroughly", "compare X vs Y in depth", or needs synthesis across multiple sources with verification. It spawns a coordinated team of researcher agents across multiple rounds…
audit-permissions
This skill should be used when the user asks to "audit claude permissions", "audit permissions", "review local claude settings", "promote permissions to global", "clean up claude settings", "find permission patterns", or wants to identify project-local Claude Code permissions that should be added to global…
malo-find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
start
Enable auto TTS for this session.
stop
Disable auto TTS for this session.