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.00028 | $0.01442 |
| Opus 5 | $0.00014 | $0.00721 |
| Sonnet 5 | $0.00006 | $0.00288 |
| Haiku 4.5 | $0.00003 | $0.00144 |
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 3d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo health
Overview
Single periodic command that combines:
- The 12-asset readiness scorecard (
scripts/repo-health-score.sh) — bounded checklist with🟩🟨⬜icons and a medal (🥉🥈🥇🏆). - PR review mining (
scripts/pr-review-mine.sh) — repeated reviewer-feedback phrases from the last N merged PRs, suggest-only. - A top-3 actionable changes summary derived from the two above.
Writes the combined report to .claude/repo-health-latest.md (always) and .claude/repo-health-latest.json (with --json). Both files are gitignored.
When To Use
- The engineer asks: "is this repo AI-ready?", "repo health", "readiness scorecard", "what should we improve?", "mine our PRs".
- As a periodic check (weekly / monthly retro) — no schedule enforcement, run when useful.
- Before a major release — confirm baseline hasn't drifted.
- After running
/mtk-setup --audit— see whether tagged principles bumped asset #2.
When NOT To Use
- For toolkit adoption analytics (who's using which MTK skills) → that's
toolkit-health. - During implementation of a feature — this is a diagnostic, not part of the build loop.
- When a repo is brand new with <3 merged PRs — mining will be empty and the scorecard will mostly fail. Run
/mtk-setupfirst.
Workflow
-
Parse flags. Accept:
--prs N(1..50, default 10) — number of merged PRs the mining step scans.--json— also write.claude/repo-health-latest.json.--no-mining— skip the PR mining step (scorecard only).
-
Run the scorecard. Always.
bash scripts/repo-health-score.shCapture stdout — this is the first half of the report.
2b. Run audit-drift check on stamped docs. Best-effort, non-blocking.
for doc in CLAUDE.md .claude/references/architecture-principles.md .claude/references/conventions.md; do
[ -f "$doc" ] || continue
bash scripts/audit-drift-check.sh "$doc" || true # exit 1 = drift, captured for report
done
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.
- 3d ago Changed efe3562b8dc8
- 12d 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 (7 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 1,442 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…