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/liortesta/ClawdAgentWrote 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/liortesta/clawdagent/ship)<a href="https://agentmods.dev/commands/liortesta/clawdagent/ship"><img src="https://agentmods.dev/badge/commands/liortesta/clawdagent/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/commands/liortesta/clawdagent/ship"><img src="https://agentmods.dev/badge/commands/liortesta/clawdagent/ship.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.00000 | $0.00421 |
| Opus 5.5 | $0.00000 | $0.00168 |
| Sonnet 5.5 | $0.00000 | $0.00084 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
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 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
Pre-Ship Quality Gates
Before merging or deploying, run ALL of the following checks. Every gate must pass.
Quality Gates:
- Tests: Run full test suite (unit + integration + E2E) — ZERO failures required
- Type Check: Run type checker (tsc --noEmit / mypy / etc.) — ZERO errors required
- Lint: Run linter — ZERO errors required (warnings acceptable)
- Security: Run dependency audit (npm audit / pip audit) — no critical/high vulnerabilities
- Build: Run production build — must complete successfully
- Performance: Run benchmarks if they exist — no regressions beyond 5%
- Docs: Check that README and API docs reflect current changes
- Dependencies: Invoke the dependency-guardian agent — no critical/high vulnerabilities, no unused deps
Process:
- Run all checks above in parallel where possible
- Collect results from all gates
- Generate a status report
Output Format:
## Ship Readiness Report
| Gate | Status | Details |
|------|--------|---------|
| Tests | PASS/FAIL | X passed, Y failed |
| Types | PASS/FAIL | X errors |
| Lint | PASS/FAIL | X errors, Y warnings |
| Security | PASS/FAIL | X vulnerabilities |
| Build | PASS/FAIL | Build time: Xs |
| Performance | PASS/FAIL/SKIP | Regression: X% |
| Docs | PASS/WARN | Up to date: yes/no |
| Dependencies | PASS/FAIL | X critical, Y outdated, Z unused |
**VERDICT**: READY TO SHIP / BLOCKED (fix X issues)
Rules:
- BLOCK if ANY critical gate fails — do not proceed
- If blocked, list EXACTLY what needs to be fixed
- Do NOT auto-fix issues here — just report. Use /self-heal to fix.
$ARGUMENTS
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 · 44 lines · 0 tokens per session scan A ab0005e7bc46
ship is a command published in the GitHub repository liortesta/ClawdAgent (11 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 421 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-30.
Other commands, from other repositories
judge-ci-red
Load when: loom-daemon forge wait-checks printed LOOM-CHECKS-RED, or post-verdict.sh … approved exited 6, and a CI-failing verdict is next.
write-test-plan
Generate or update change test plan.
test-setup
Scaffold test framework and CI pipeline.
ci-setup
Setup CI pipeline from scratch. Creates GitHub Actions or GitLab CI configuration with lint, test, build, and deploy stages.
harness:cicd-fleet
Autonomous CI/CD-remediation orchestrator — triage the red CI/CD-run and flaky-test backlog by cause, fan out worktree-isolated subagents that run the real deflake/heal pipeline, independently verify each fix by artifact and deterministic all-OS CI, and hand back a batch of remediation PRs for one bulk human review.…
check-fix
Execute quality gates, fix any issues found, and create a single high-quality Conventional Commit summarizing all changes made.