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 xiehuan123/coding-coach --skill researchgit clone --depth 1 https://github.com/xiehuan123/coding-coachWrote 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/xiehuan123/coding-coach/research)<a href="https://agentmods.dev/skills/xiehuan123/coding-coach/research"><img src="https://agentmods.dev/badge/skills/xiehuan123/coding-coach/research.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.00055 | $0.00175 |
| Opus 5 | $0.00028 | $0.00088 |
| Sonnet 5 | $0.00011 | $0.00035 |
| Haiku 4.5 | $0.00006 | $0.00017 |
Grade A, and why
research 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 12 lines · 55 tokens per session scan A 2fb5ff4a2c75
research is a skill published in the GitHub repository xiehuan123/coding-coach (4 stars, last pushed 23d ago), with no licence file. It adds 55 tokens to every session and 175 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 skills, from other repositories
project-blueprint
A workflow for setting up coding rules and project documentation for a new software project. It examines the existing files to infer the languages, frameworks, commands, testing practices, and Git conventions.
event-review
A weekly review process for event logs and leftover task records, turning repeated problems or useful lessons into proposed memory, knowledge, or skill entries.
gan-zhong-xue
A learning workflow that makes an AI explain code changes through questions, evidence, and underlying principles. It is designed to help developers understand work they asked an AI to do, rather than merely accept the result.
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.