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 rdudov/task-agent --skill repo-healthgit clone --depth 1 https://github.com/rdudov/task-agentWrote 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/rdudov/task-agent/repo-health)<a href="https://agentmods.dev/skills/rdudov/task-agent/repo-health"><img src="https://agentmods.dev/badge/skills/rdudov/task-agent/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/rdudov/task-agent/repo-health"><img src="https://agentmods.dev/badge/skills/rdudov/task-agent/repo-health.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.00055 | $0.01023 |
| Opus 5 | $0.00028 | $0.00511 |
| Sonnet 5 | $0.00011 | $0.00205 |
| Haiku 4.5 | $0.00006 | $0.00102 |
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 10d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Health
This skill checks whether the repository is structurally usable after restore or before handoff.
Scope
Use it when:
- a backup restore may have lost local artifacts
- a public/template copy is being prepared
- task, data, or skill structure has changed
- an agent-engine change needs a quick repository health gate
Checks
The bundled script validates:
- required root files:
AGENTS.md,README.md,.gitignore,requirements.txt, andrequirements.lock - required docs:
docs/architecture.mdanddocs/task-execution.md - every task directory has
task.mdandplan.md. The rebuildable task index is deliberately not checked: it is regenerated fromtasks/on demand, andtasks_index.py checkowns the task-metadata properties - every
skills/*/SKILL.mdhasnameanddescriptionfrontmatter - executable Python scripts parse in memory, so the check works on read-only
checkouts and does not create
__pycache__entries - obvious secret-like content is absent from the files Git can publish: tracked files plus untracked, non-ignored files. The check reuses the pre-push guard's pattern definitions and fails closed if Git cannot establish that scope.
Ignored tasks/ and data/ contain durable local evidence, not publishable
source. Repository health therefore does not scan those histories for secrets;
check_pre_push.py still refuses real task/data artifacts in outgoing commits.
Command
.venv/bin/python skills/repo-health/scripts/check_repo_health.py
For a sanitized template that intentionally omits local task history:
.venv/bin/python skills/repo-health/scripts/check_repo_health.py --allow-empty-tasks
Pre-Push Leak Check
Run before pushing source changes to a configured remote:
.venv/bin/python skills/repo-health/scripts/check_pre_push.py --remote origin
The check scans outgoing files for local task/data/state artifacts, environment files, private keys, and common token formats. It is a guardrail, not a complete security scanner; still review the outgoing diff before pushing.
What ships with it
7 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.
- scripts/check_deliverables.py 6.6 KB runs code
- scripts/check_pre_push.py 9.8 KB runs code
- scripts/check_repo_health.py 12 KB runs code
- tests/test_check_deliverables.py 7.2 KB runs code
- tests/test_check_pre_push.py 5.3 KB runs code
- tests/test_check_repo_health.py 7.6 KB runs code
- tests/test_entry_point_wiring.py 6.9 KB runs code
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.
- 10d ago First seen · 96 lines · 55 tokens per session scan A 6405b8bbe9ee
repo-health is a skill published in the GitHub repository rdudov/task-agent (4 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 1,023 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.