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/validate)<a href="https://agentmods.dev/commands/vimalk0703/shipworthy/validate"><img src="https://agentmods.dev/badge/commands/vimalk0703/shipworthy/validate/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/vimalk0703/shipworthy/validate"><img src="https://agentmods.dev/badge/commands/vimalk0703/shipworthy/validate.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.00401 |
| Opus 5.5 | $0.00000 | $0.00160 |
| Sonnet 5.5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
validate 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
Before executing this command, output:
⚓ shipworthy › command:
/validate— running pre-push validation suite
/validate — Pre-Push Validation Gate
Run the comprehensive Shipworthy validation suite before pushing changes.
What This Does
Dispatches the pre-push-validator agent to run all validation checks against the current state of the repository. This catches issues before they reach CI.
Steps
- Run
bash tests/validate-all.shto execute the full validation suite - Report results grouped by category:
- Hook tests — session-start, pre-tool-use, post-tool-use (37 tests)
- Skill frontmatter — name, description, invoke_when fields on all skills
- CSO compliance — invoke_when starts with "Use when...", length limits, name/directory match
- Skill routing — all skills reachable from the master routing table
- Cross-references — all shipworthy:skill-name references resolve to real skills
- Skill quality — no duplicates, minimum content, anti-patterns sections, markdown structure
- Repo structure — required files, directories, agents, templates, commands, secrets scan
- If any check fails, list the specific failures and suggest fixes
- If all checks pass, confirm it is safe to push
When to Run
- Before every
git push - After adding or modifying skills
- After changing hooks
- Before creating a PR
- When the user runs
/validate
Output Format
Report results as a clear summary table:
| Check | Status | Details |
|---|---|---|
| Hook tests | PASS/FAIL | 37/37 passed |
| Skill frontmatter | PASS/FAIL | 55/55 valid |
| CSO compliance | PASS/FAIL | All "Use when..." |
| ... | ... | ... |
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 · 46 lines · 0 tokens per session scan A 66756f0fd103
validate is a command published in the GitHub repository Vimalk0703/shipworthy (6 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 401 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
work-flow-feature
Complete workflow for developing a new feature, from exploration to merge.
dare-laravel-api
Padrões DARE para APIs REST em Laravel 11 + PHP 8.3. Strict Types, FormRequests, Services, Resources, Repositories, Eloquent + casts, tratamento global de exceções, testes Pest, PHPStan/Larastan nível 8.
dare-execute
Executa uma task específica do DARE/dare-dag.yaml seguindo o Ralph Loop.
dare-migrate
Camada semântica da migração (Fase 2 brownfield). Roda depois de dare migrate, que já leu os artefatos do reverse/dna e gerou os esqueletos. Sua função é escrever a estratégia de migração e os cenários Gherkin de paridade reais — o contrato comportamental que garante uma reimplementação fiel ao legado.
dare-bench
Roda o harness determinístico de fixtures de verificação (dare bench) — mede Fix·Rate e solve-rate contra patches versionados.
ccc-verify
Verify the current codebase in a fixed order (build, types, lint, tests with coverage, secrets, debug logs, git status) and return a PASS/FAIL report with a ready-for-PR verdict. Use before committing, before opening a PR, or when asked to check that everything still works.