Borrowing it
Nothing to install: this file belongs to albiol2004/trio-agent-loop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/albiol2004/trio-agent-loop/main/.claude/skills/trio-ship/SKILL.mdgit clone --depth 1 https://github.com/albiol2004/trio-agent-loopWrote 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/albiol2004/trio-agent-loop/trio-ship)<a href="https://agentmods.dev/skills/albiol2004/trio-agent-loop/trio-ship"><img src="https://agentmods.dev/badge/skills/albiol2004/trio-agent-loop/trio-ship.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.00000 | $0.00453 |
| Opus 5 | $0.00000 | $0.00227 |
| Sonnet 5 | $0.00000 | $0.00091 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
trio-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 8d 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
A SHIP verdict normally ends with the Evaluator's retirement commit: one
product commit slice(<id>): <summary> plus one mailbox commit
loop: iteration N — SHIP, recorded as commit: lines in loop/VERDICT.md.
If a verdict says SHIP but those commits never landed (a legacy or orphaned
run), recover it yourself — the same two-commit pattern, using the verdict's
own suggested commit message. No subagent and no model config: you run the git
commands directly.
Mailbox directory: default loop/. If invoked with dir=<path>, that
directory is the mailbox — every loop/ reference below means it.
- Read
loop/VERDICT.md. Its first non-empty line must beVERDICT: SHIP; otherwise STOP and tell the user the verdict is not machine-readable. - Take the suggested commit message from the verdict's
## Guidance for next iterationsection. - Check
git status. Clean tree → there is no product commit to make; recordcommit: <HEAD sha>and jump to step 6. - Commit the product changes attributable to the loop in one commit:
git add <those paths>thengit commit -m "slice(<id>): <summary>"(the suggested message, shaped to the slice convention; other slice ids in the body). Leave unrelated changes uncommitted and flag them to the user — never sweep foreign paths in. - Append
commit: <product sha>toloop/VERDICT.md. - Commit the mailbox:
git add loop/thengit commit -m "loop: iteration N — SHIP"(iteration N from STATE.md). - Confirm and report both shas to the user (
git rev-parsethe product commit and the mailbox commit).
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.
- 8d ago First seen · 34 lines · 0 tokens per session scan A 04ae78bc231a
trio-ship is a skill published in the GitHub repository albiol2004/trio-agent-loop (2 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 453 tokens. 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
github-commenting
How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules. Load before posting or fixing any PR comment.
commit
Read this skill before making git commits.
contextual-commit
Write contextual commits that capture intent, decisions, and constraints alongside code changes. Use when committing code, finishing a task, or when the user asks to commit. Extends Conventional Commits with structured action lines in the commit body that preserve WHY code was written, not just WHAT changed.
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.
security-pipeline
Use when security verification is needed - pre-commit security checks, vulnerability scanning, STRIDE threat analysis. Integrates with /handoff-verify --security and /commit-push-pr. CWE Top 25 based.
commit-and-push
Create a well-formatted git commit and push to remote repository.