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/pr-fleet)<a href="https://agentmods.dev/commands/intense-visions/harness-engineering/pr-fleet"><img src="https://agentmods.dev/badge/commands/intense-visions/harness-engineering/pr-fleet.svg" alt="Measured on agentmods" 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.00078 | $0.00575 |
| Opus 5 | $0.00039 | $0.00287 |
| Sonnet 5 | $0.00016 | $0.00115 |
| Haiku 4.5 | $0.00008 | $0.00057 |
Grade A, and why
harness:pr-fleet 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 4d 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:
- select: Enumerate the open-PR queue, triage each PR into the land-readiness taxonomy, cross-check for superseded/already-resolved PRs, and order landable candidates by land-priority
- confirm: Present the triaged queue in one round — superseded items flagged for closure, decision forks as questions, proposed concurrency — for a single up-front human approval that carries the per-PR merge authorization
- dispatch: Fan out worktree-isolated subagents that each run the real code-review pipeline for one PR, push fix commits for mechanical findings, and re-run CI — never merging, never fabricating approval — capped at the concurrency governor
- verify: Independently confirm each PR proposed to land is CI-green across all target operating systems plus the project's required checks, carries a review verdict, and is mergeable — never by subagent self-report
- land: Merge only the PRs that are both human-approved in confirm and independently verified, honoring branch protection; emit a one-row-per-PR batch summary and close superseded PRs citing the superseding PR; never merge unapproved or unverified work
<execution_context> @agents/skills/claude-code/pr-fleet/SKILL.md @agents/skills/claude-code/pr-fleet/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.
- 4d ago First seen · 41 lines · 78 tokens per session scan A 617246c9fbf9
harness:pr-fleet is a command published in the GitHub repository Intense-Visions/harness-engineering (20 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 575 once invoked, about $0.0004 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-09-03.
Other commands, from other repositories
release-readiness
Trigger a pre-merge release readiness review on a GitHub PR, GitLab MR, or local branch.
release
Release manager for frontend and mobile. Writes App Store notes, user-facing changelog, flags stale docs and landing copy. Actions: notes | changelog | docs | sync.
release
Bump version, commit, push, mirror to ai-skills, and update local plugin.
ship
Branch, commit, open PR, gather Claude + every enabled AI reviewer (Copilot, CodeRabbit, etc.), fix/justify/resolve every finding, loop until clean, then merge. Run only when implementation is finished AND the owner has said to ship (e.g. "ship it") — never self-invoke just because the work looks done. To design and…
release-kick
A release command for the River Review project that checks release instructions and pull-request state, updates an out-of-date branch, and verifies the release after merging.
ship
Pre-ship pipeline — test, review, then prepare a clean commit.