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/alinotfoundbtw/soundingWrote 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/alinotfoundbtw/sounding/ship)<a href="https://agentmods.dev/commands/alinotfoundbtw/sounding/ship"><img src="https://agentmods.dev/badge/commands/alinotfoundbtw/sounding/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/alinotfoundbtw/sounding/ship"><img src="https://agentmods.dev/badge/commands/alinotfoundbtw/sounding/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.00007 | $0.00231 |
| Opus 5.5 | $0.00003 | $0.00092 |
| Sonnet 5.5 | $0.00001 | $0.00046 |
| Haiku 4.5 | $0.00001 | $0.00023 |
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
Prepare release $ARGUMENTS. Do not push a tag and do not publish anything without explicit confirmation.
- Run
/check. Stop if anything fails. - Bump the version in
src/sounding/__init__.pyandpyproject.toml. They must match. - Rebuild the playground wheel and re-embed it:
then replacerm -f playground/*.whl python -m build --wheel --outdir playground/WHEEL_B64inplayground/index.htmlwith the new base64. Verify the embedded bytes start withPK. - Re-read the README top to bottom. Every claim must be true of this version — test counts, rule counts, feature list, roadmap marker. Fix anything stale.
- Draft release notes: Added / Changed / Fixed, each line saying what it means for someone using the tool.
- Show me the diff and the notes. Wait for approval before tagging.
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 · 24 lines · 7 tokens per session scan A f3275f5612ca
ship is a command published in the GitHub repository alinotfoundbtw/sounding (4 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 231 once invoked, about $0.0000 per session on Opus 5.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-31.
Other commands, from other repositories
release
Prepara e pubblica una nuova release del plugin mcp-legal-it. Bumpa la versione in tutti i manifest, aggiorna i changelog e la description con il conteggio tool corretto, crea il release branch, merge in main e tagga.
gsd:ship
Create PR, run review, and prepare for merge after verification passes.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
release-swarm
Orchestrate complex software releases using AI swarms that handle everything from changelog generation to multi-platform deployment.
sync-coordinator
Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages.
gsd:complete-milestone
Archive completed milestone and prepare for next version.