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 stark-ai-de/agent-skills --skill repo-health-auditgit clone --depth 1 https://github.com/stark-ai-de/agent-skillsWrote 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/stark-ai-de/agent-skills/repo-health-audit)<a href="https://agentmods.dev/skills/stark-ai-de/agent-skills/repo-health-audit"><img src="https://agentmods.dev/badge/skills/stark-ai-de/agent-skills/repo-health-audit/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/stark-ai-de/agent-skills/repo-health-audit"><img src="https://agentmods.dev/badge/skills/stark-ai-de/agent-skills/repo-health-audit.svg" alt="Reviewed on agentmods" width="80" 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.00049 | $0.00652 |
| Opus 5 | $0.00024 | $0.00326 |
| Sonnet 5 | $0.00010 | $0.00130 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
repo-health-audit 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 12d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Health Audit
Goal
Produce a structured maintenance report that separates urgent repository risks from polish, identifies gaps in onboarding and automation, and recommends the next practical maintainer actions.
When to use
- The user asks whether a repository is healthy, maintainable, or ready to publish.
- A repo needs a maintainer audit across docs, tests, CI, releases, and security hygiene.
- The user wants a prioritized cleanup plan without immediate code edits.
When not to use
- The user asks for a focused PR review; use
pr-review. - The task is only documentation clarity; use
docs-audit. - The user already asked for implementation instead of audit.
Inputs to inspect
- README, docs, examples, changelog, license, security policy, and contribution guide.
- Package files, lockfiles, test config, format/lint config, and validation scripts.
- CI workflows, issue templates, release automation, and dependency update config.
- Current
git status, recent commits, and validation output when available.
Review rubric
Score docs, build/test, CI, release readiness, dependency hygiene, security baseline, issue/PR operations, and agent context from 0 to 5. Read references/audit-rubric.md for scoring detail and references/report-template.md for the report shape.
Workflow
- Inspect top-level files and repository structure.
- Identify the main stack and validation commands.
- Review docs against actual commands and files.
- Check CI, release, security, and contribution surfaces.
- Run safe validation commands when the user expects implementation-level evidence.
- Produce a scored report with urgent issues, quick wins, backlog items, and the next action.
Safety rules
- Do not change repository files unless the user explicitly asks for implementation.
- Do not print secrets or sensitive config values in the audit.
- Mark live repository settings as unverified unless they were checked directly.
References
Read only when needed:
What ships with it
2 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.
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.
- 12d ago First seen · 89 lines · 49 tokens per session scan A 4d29df53780a
repo-health-audit is a skill published in the GitHub repository stark-ai-de/agent-skills (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 49 tokens to every session and 652 once invoked, about $0.0002 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
workspace
Multi-repo workspace coordinator for shared team context. Initialize .adlc/ structure, configure .gitignore, discover child repos, link them as Git submodules, and audit workspace health. Use --init for first-time setup, default mode for ongoing auditing.
product-roadmap
Track milestone progress across four layers of truth — decision state (PDR status), execution state (live issue tracker via MCP), evidence state (code-vs-PDR verification), and gate state (milestone gates). Shows honest completion, done-means warnings, and updates status only when all layers are green. Use for weekly…
product-clarify
Refine and validate Product Decision Records through targeted clarification questions. Review PDR completeness, detect conflicts, approve decisions, and update status to Accepted. Use before /product-implement.
status
Show active or recent Claude Code jobs in this repository, or detailed status for a specific job id. Args: [job-id], --wait, --timeout-ms , --poll-interval-ms , --all. Use for tracked-job inspection, not setup or result retrieval.
session-close
Close a coding-agent session with durable repository state, proportional verification, documentation reconciliation, and a useful handoff. Use when the user says close out, wrap up, end session, session report, doc sync, preserve work, or asks for a final commit and push before stopping.
completion-report
Write a completion report with files changed, tests run, results, skipped checks, docs updated, remaining risks, and release readiness notes. Use when recording evidence that a task or feature is complete and ready for review.