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/hybridlabor-api/bdb-dev-optimized-agent-skillsWrote 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/agents/hybridlabor-api/bdb-dev-optimized-agent-skills/godmode-shipping)<a href="https://agentmods.dev/agents/hybridlabor-api/bdb-dev-optimized-agent-skills/godmode-shipping"><img src="https://agentmods.dev/badge/agents/hybridlabor-api/bdb-dev-optimized-agent-skills/godmode-shipping.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.00121 | $0.00338 |
| Opus 5 | $0.00060 | $0.00169 |
| Sonnet 5 | $0.00024 | $0.00068 |
| Haiku 4.5 | $0.00012 | $0.00034 |
Grade A, and why
godmode-shipping 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
Release Gatekeeper, QA & Verification Auditor. Runs the automated quality gate (lint, typecheck, tests, a11y, seo) after Reviewer's findings are all fixed/wont_fix — Reviewer and Shipping are deliberately two different checks (adversarial correctness review vs. mechanical gate execution), not one merged step. Ensures pre-launch checks, automated web testing, SEO compliance, WCAG accessibility, and clean git history before production release. Never ships with an open blocking finding or without a GO in state.approvals.
Primary skills: godmode-shipping, webapp-testing, seo-audit, wcag-audit-patterns, github-repo, clean-code
MCP servers used: github, chrome-devtools
Output artifact(s): production_artifacts/04_release_report.md
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 · 14 lines · 121 tokens per session scan A 8b1ee2f4b58a
godmode-shipping is an agent published in the GitHub repository hybridlabor-api/bdb-dev-optimized-agent-skills (6 stars, last pushed 3d ago), licensed Apache-2.0. It adds 121 tokens to every session and 338 once invoked, about $0.0006 per session on Opus 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 agents, from other repositories
oma-verifier
Use for acceptance-gate verification, test evidence checks, and release-readiness decisions.
release-changelog-composer
Compose the prose of one release cut from the records that shipped in it — every line citing the record id it reports, so the binary can prove the release record describes exactly the cut. Host-delegated; feeds abcd launch ship --changelog-json.
tester
Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…
release-prep
Use this agent to autonomously prepare a project release by running pre-release checks, validating CI, checking test coverage, and verifying changelog. Triggers on "prepare release", "pre-release check", "ready to release", or when validating release readiness.
doc-changelog
Changelog maintenance following Keep a Changelog. Use to document changes between versions.
formatter
Use when the parity-test-e pipeline needs to render a concise markdown release summary from extracted changelog entries produced by the extractor step.