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 Ancienttwo/repo-harness --skill repo-harness-shipgit clone --depth 1 https://github.com/Ancienttwo/repo-harnessWrote 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/ancienttwo/repo-harness/repo-harness-ship)<a href="https://agentmods.dev/skills/ancienttwo/repo-harness/repo-harness-ship"><img src="https://agentmods.dev/badge/skills/ancienttwo/repo-harness/repo-harness-ship/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/ancienttwo/repo-harness/repo-harness-ship"><img src="https://agentmods.dev/badge/skills/ancienttwo/repo-harness/repo-harness-ship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 32 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00039 | $0.00649 |
| Opus 5 | $0.00019 | $0.00324 |
| Sonnet 5 | $0.00008 | $0.00130 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
repo-harness-ship 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
repo-harness-ship
Use this command when implementation is complete and the user wants the harness to close out worktrees and create reviewable PRs.
Protocol
- Run worktree safety preflight with
git status --short --branch -uallandgit worktree list --porcelain. - In default PR mode, run
repo-harness run ship-worktrees; it validates review/check evidence, runsrepo-harness run contract-worktree finish --no-merge, pushescodex/<slug>, and creates a draft PR withgh pr create --base main --head codex/<slug>. - For a dirty target branch that is explicitly attributable to the active plan, pass
--slug <slug>so the script createscodex/<slug>-main-closeoutand opens a PR instead of committing tomain. - For maintainer-only local closeout, run
repo-harness run ship-worktrees --local-merge; this preserves the olderfinish-> fast-forwardmain->cleanuppath. - After a PR has merged and local
maincontains the branch, runrepo-harness run ship-worktrees --cleanup-mergedto remove only proven-merged local worktrees and branches. If the branch is merged but the linked worktree is dirty, pick/apply/commit useful changes first; use--discard-scaffold-onlyonly when the dirty paths are generated plan/contract/review/notes scaffold.
CHECKPOINTS
- CHECKPOINT: before push, PR creation, local merge, or cleanup, verify review, external acceptance, and
verify-sprintevidence are present and passing.
Failure Modes
- If the target worktree is dirty with unrelated files, stop and report the dirty paths.
- If a PR already exists, reuse it instead of creating a duplicate.
- If cleanup finds a dirty merged worktree, preserve useful changes or use
--discard-scaffold-onlyonly for generated scaffold files.
Boundaries
- Default mode creates PRs; it does not fast-forward
main, merge PRs, publish releases, or tag versions. - Does not run
git reset --hard,git clean, or automatic stash. - Does not treat
_opstgz archives as a successful closeout path; merged dirty worktrees must be committed/picked/applied or explicitly discarded as scaffold-only. - Does not commit, push, open PRs, or cleanup when Waza
/check, external acceptance, orverify-sprintevidence is missing or failing. - Does not absorb unrelated dirty target or sibling worktree changes.
- Re-reads existing PR state after a create failure or before creating a new PR to avoid duplicates.
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 · 37 lines · 39 tokens per session scan A 59926ef29068
repo-harness-ship is a skill published in the GitHub repository Ancienttwo/repo-harness (431 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 649 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-30.
Other skills, from other repositories
release
Cut and publish a full stable NAC release after main, release-PR, and publication CI pass. Use when a maintainer asks for a stable version bump, tag, or GitHub Release. Never use for release candidates; NAC RC releases are automated.
graincrawl
Maintain, verify, and release graincrawl, the local-first Granola archive CLI, including SQLite archive behavior, read-only Granola source boundaries, Homebrew tap packaging, and crawlkit-powered TUI/snapshot surfaces.
crawlkit
Maintain and release the crawlkit Go library, preserving downstream compatibility for gitcrawl, slacrawl, discrawl, and notcrawl.
publish-pr
Use in /implement at the draft→ready boundary to squash the branch's review-iteration commits into one (non-interactive soft-reset + recommit + force-with-lease) and mark the draft PR ready. Takes the commit message as input (sourced from the plan-file before cleanup). GitHub-specific (gh) behind a host-neutral…
github-release-briefing-skill
Create a source-linked briefing for the latest published GitHub release of a public repository. Use for engineering teams tracking a dependency release; do not use it to publish releases or change repositories.
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.