Borrowing it
Nothing to install: this file belongs to moberghr/mtk-agent-toolkit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/moberghr/mtk-agent-toolkit/main/.claude/skills/repo-health/SKILL.mdgit clone --depth 1 https://github.com/moberghr/mtk-agent-toolkitWrote 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/moberghr/mtk-agent-toolkit/repo-health)<a href="https://agentmods.dev/skills/moberghr/mtk-agent-toolkit/repo-health"><img src="https://agentmods.dev/badge/skills/moberghr/mtk-agent-toolkit/repo-health/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/moberghr/mtk-agent-toolkit/repo-health"><img src="https://agentmods.dev/badge/skills/moberghr/mtk-agent-toolkit/repo-health.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 62 Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
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.00034 | $0.01054 |
| Opus 5.5 | $0.00014 | $0.00422 |
| Sonnet 5.5 | $0.00007 | $0.00211 |
| Haiku 4.5 | $0.00003 | $0.00105 |
Grade A, and why
repo-health 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 16d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo health
Overview
One report from three scripts — repo-health-score.sh (nine assets, pass/partial/fail/na plus action_needed; no medal or aggregate; assets 5–6 read na outside the MTK checkout; rubric in .claude/references/repo-health-assets.md), audit-drift-check.sh, and pr-review-mine.sh (imperative reviewer phrases recurring across ≥2 merged PRs, tagged [MINED:feedback], suggest-only; heuristics and denylist in .claude/references/pr-mining-patterns.md).
Writes .claude/repo-health-latest.md (always) and .claude/repo-health-latest.json (with --json); both are gitignored.
When To Use
- "Is this repo AI-ready?", "repo health", "what should we improve?", "mine our PRs", "what do reviewers keep asking for?"
- Periodically, before a major release, or after
/mtk-setup --audit.
When NOT To Use
- MTK usage numbers →
mtk-doctor --usage. - Inside the build loop, or on a repo with fewer than 3 merged PRs (mining has no signal; run with
--no-mining).
Workflow
-
Flags.
--prs N(1..50, default 10),--json,--no-mining. -
Checklist.
bash scripts/repo-health-score.sh(add--jsonfor the JSON file). The nine assets are canonical; never add, drop or re-grade one at runtime — a change goes through the reference and the script. -
Audit drift (best-effort, never blocks):
CONST_DOC=AGENTS.md; [ -f "$CONST_DOC" ] || CONST_DOC=CLAUDE.md for doc in "$CONST_DOC" .claude/references/architecture-principles.md .claude/references/conventions.md; do [ -f "$doc" ] || continue bash scripts/audit-drift-check.sh "$doc" || true # exit 1 = drift doneDrift annotates asset 2 as
🟨 audit drift: N citations; it never changes the status. Unstamped docs are skipped silently. -
Mining (unless
--no-mining):bash scripts/pr-review-mine.sh --prs <N>. Fail-soft: without an authenticatedghit printsSkipped: <reason>and exits 0 — report that line, never phrases from memory. A phrase needs ≥2 distinct PRs; one reviewer repeating it in one PR is not a team norm. Boilerplate that slips through ("great work") goes on the## Denylistofpr-mining-patterns.md, then re-run; the denylist is never bypassed for one run.
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.
- 16d ago Changed · -56 lines · +6 tokens per session 0d5b94504de9
- 1mo ago Changed efe3562b8dc8
- 2mo ago First seen · 118 lines · 28 tokens per session scan A 86d184cfd5d9
repo-health is a skill published in the GitHub repository moberghr/mtk-agent-toolkit (9 stars, last pushed 8d ago), licensed MIT. It adds 34 tokens to every session and 1,054 once invoked, about $0.0001 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…