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.
git clone --depth 1 https://github.com/Intense-Visions/harness-engineeringWrote 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/commands/intense-visions/harness-engineering/maintenance-pipeline)<a href="https://agentmods.dev/commands/intense-visions/harness-engineering/maintenance-pipeline"><img src="https://agentmods.dev/badge/commands/intense-visions/harness-engineering/maintenance-pipeline/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/commands/intense-visions/harness-engineering/maintenance-pipeline"><img src="https://agentmods.dev/badge/commands/intense-visions/harness-engineering/maintenance-pipeline.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.00041 | $0.00324 |
| Opus 5.5 | $0.00016 | $0.00130 |
| Sonnet 5.5 | $0.00008 | $0.00065 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
harness:maintenance-pipeline 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 1mo 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.
What it actually says
Phases:
- sweep: Run
harness maintenance run --json(overdue, report mode) and parse the consolidated report - triage: Present a human-readable summary bucketed by status and findings count
- fix: Ask the human in plain text which tasks to fix, then re-invoke
--only <ids> --fixand relay the result (optional)
<execution_context> @agents/skills/claude-code/harness-maintenance-pipeline/SKILL.md @agents/skills/claude-code/harness-maintenance-pipeline/skill.yaml </execution_context>
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.
- 1mo ago First seen · 37 lines · 41 tokens per session scan A be2192f6133f
harness:maintenance-pipeline is a command published in the GitHub repository Intense-Visions/harness-engineering (22 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 324 once invoked, about $0.0002 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-09-03.
Other commands, from other repositories
bug-report
Draft a bug report issue for lean4-skills.
triage
Query open Node bugs, classify by priority and sub-team, suggest assignments, and generate a triage summary.
speckit.companion.doctor
Report on a spec's run health — unfinished steps, unjournaled tasks, step bleed, drift you can judge, a step that closed having verified nothing, a step that closed without the file it promised, and why completion did not land (read-only, retroactive, never halts).
postmortem
Deliver a structured post-mortem after incidents, mistakes, or stuck sessions. Use when the user requests a structured post-mortem after incidents, mistakes, or stuck sessions.
audit
Audit closed tickets for regressions against today's code (unchanged, evolved, implemented wrong, not implemented), plus duplicate and groupable open ones.
forense
Investigação post-mortem de workflows framework com falha — analisa histórico git, artefatos e estado para diagnosticar o que deu errado.