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 bh-rat/steer --skill repo-healthgit clone --depth 1 https://github.com/bh-rat/steerWrote 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/bh-rat/steer/repo-health)<a href="https://agentmods.dev/skills/bh-rat/steer/repo-health"><img src="https://agentmods.dev/badge/skills/bh-rat/steer/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/bh-rat/steer/repo-health"><img src="https://agentmods.dev/badge/skills/bh-rat/steer/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.00043 | $0.01068 |
| Opus 5 | $0.00022 | $0.00534 |
| Sonnet 5 | $0.00009 | $0.00214 |
| Haiku 4.5 | $0.00004 | $0.00107 |
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 11d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
repo-health
Produce a one-page health report for the repository in the current
workspace: recent commit activity, what the codebase is made of, how much
marked debt (TODO/FIXME) it carries, and whether tests exist. The result
the user gets is out/health/REPORT.md, with trends against the previous
run.
This skill bundles its own steer runtime at scripts/steer.py; the
commands below invoke it with python3 and need nothing installed.
Paths are relative to this skill's directory: when your working
directory is elsewhere (it usually is), use the skill's full path
(python3 <path-to-this-skill>/scripts/steer.py ...).
Before you start
- Ground yourself. Run
python3 scripts/steer.py contextand read the snapshot before doing anything else; it tells you the platform, project type, git state, and which tools exist here. - Apply past lessons. Run
python3 scripts/steer.py learn showand follow what it says; those lessons came from real previous runs. - Check credentials, only when the user wants the summary posted to
their webhook (
scripts/share.py). Runpython3 scripts/steer.py secrets check REPO_HEALTH_WEBHOOK. If it is missing, ask the user to runpython3 scripts/steer.py secrets set REPO_HEALTH_WEBHOOK(never ask them to paste the value into the chat), then re-check.
Process
This skill has an enforced flow: steps verify themselves against reality, and you cannot skip ahead.
- Announce: "Working through the repo-health flow."
- Run
python3 scripts/steer.py flow status(in the workspace) to see progress and the current step. - Do what the directive says. Steps with a verify condition complete
automatically once reality matches; for mandate steps, mark completion
with
python3 scripts/steer.py flow done <step-id>. - Run
python3 scripts/steer.py flow nextand repeat until it reports all steps complete.
Do NOT claim the work is done while python3 scripts/steer.py flow status shows incomplete steps. The flow is defined in flow.toml.
What ships with it
5 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.
- 11d ago First seen · 103 lines · 43 tokens per session scan A 0cbb7c805e22
repo-health is a skill published in the GitHub repository bh-rat/steer (7 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 1,068 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
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…