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/Vimalk0703/shipworthyWrote 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/vimalk0703/shipworthy/health)<a href="https://agentmods.dev/commands/vimalk0703/shipworthy/health"><img src="https://agentmods.dev/badge/commands/vimalk0703/shipworthy/health.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.00615 |
| Opus 5 | $0.00000 | $0.00308 |
| Sonnet 5 | $0.00000 | $0.00123 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
health 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Before executing this command, output:
⚓ shipworthy › command:
/health— generating health dashboard
Show a comprehensive project and plugin health dashboard.
Part 1: Plugin Installation Health
Verify Shipworthy is correctly installed and functioning:
- Hooks installed: Check
hooks.jsonhas all 4 hook entries (SessionStart, PreToolUse×2, PostToolUse×2) - Hook scripts exist: All 5 hook scripts exist and are executable (
session-start,pre-tool-use,pre-tool-use-bash,post-tool-use,post-tool-use-write) - Shared library:
hooks/lib.shexists and is sourceable - JSON parser available: Check if
jqorpython3is available for robust JSON parsing - Detected tier: What tier was this project assigned? Is it correct?
- Skills loaded: How many skills are available? Any orphaned?
- Hook performance: Run session-start hook and measure execution time. Flag if >3 seconds.
- Debug mode: Is
SHIPWORTHY_DEBUG=1set? If so, check log at~/.shipworthy/debug.log
Part 2: Project Health
- Architecture spec: Present / Missing at
.shipworthy/architecture.md - Test suite: Pass / Fail / No tests found (run
npm testor equivalent) - Build status: Pass / Fail (run
npm run buildor equivalent) - Linter: Configured / Passing / Missing
- Tech debt items: Count from
.shipworthy/tech-debt.md - Dependency vulnerabilities: Count from
npm auditor equivalent - File count: Total source files (indicates quality gate level)
- Quality gate level: 0-4 based on file count and tier
- Feature specs: Count in
.shipworthy/specs/ - In-progress plans: Count in
.shipworthy/plans/
Format as a concise dashboard:
Shipworthy Health Dashboard
============================
Plugin Status
Hooks: 5/5 installed
JSON parser: jq available
Tier detected: maker
Skills loaded: 46 (0 orphaned)
Hook latency: 1.2s (OK)
Project Status
Architecture: Present
Tests: 47 passing, 0 failing
Build: Clean
Linter: ESLint — passing
Tech debt: 3 items (1 critical)
Vulnerabilities: 0 known
Source files: 42 → Quality Gate Level 2
Specs: 3 in .shipworthy/specs/
Plans: 1 in-progress
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 · 57 lines · 0 tokens per session scan A f6b42be008be
health is a command published in the GitHub repository Vimalk0703/shipworthy (7 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 615 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 commands, from other repositories
dare-bugfix-design
Diagnostica bug em projeto existente e planeja correção cirúrgica via Método DARE. Gera DARE/DESIGN-Bugfix-[Nome].md com causa raiz, riscos de regressão e plano de ação mínimo.
dare-info
Mostra versão do CLI, caminhos relevantes e a integridade da instalação DARE no projeto atual.
quick-fix
Run the implement→review subagent loop without the planning phase — for straightforward fixes with a known cause and one obvious approach, regardless of how many files the change spreads across. Skips the spec gate, worktree gate, and finalize ceremony (implementation log, docs, signals) that /subagent-implementation…
bootstrap
Verifies and repairs the Claude Code Toolkit installation.
ccc-debug-session
Start a structured debug session with hypothesis tracking and resolution documentation.
maintain
Run automated maintenance — seeker finds bugs from pod logs and raises GitHub issues, fixer picks them up and creates PRs. Can run as a one-shot or scheduled via /schedule.