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/NickRomanek/clawbridgeWrote 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/nickromanek/clawbridge/deploy)<a href="https://agentmods.dev/commands/nickromanek/clawbridge/deploy"><img src="https://agentmods.dev/badge/commands/nickromanek/clawbridge/deploy/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/nickromanek/clawbridge/deploy"><img src="https://agentmods.dev/badge/commands/nickromanek/clawbridge/deploy.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.00752 |
| Opus 5.5 | $0.00000 | $0.00301 |
| Sonnet 5.5 | $0.00000 | $0.00150 |
| Haiku 4.5 | $0.00000 | $0.00075 |
Grade A, and why
deploy scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
3. Verify `curl -s http://127.0.0.1:8765/health` returns the new version How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Full Release Deployment
Run the complete ClawBridge release process. This is the ONLY way to deploy — follow every step.
Pre-flight checks
- Confirm
/e2eand/securityhave been run this session (or run them now). - Run smoke tests against the running server:
python tests/smoke_test.py - If any tests or security checks fail, STOP and fix before deploying.
Version bump
Bump version in ALL 6 locations (skip if already bumped):
clawbridge.pyline ~14 (__version__)build.pyline ~32 (VERSION)build_macos.pyline ~36 (VERSION)installer.issline ~10 (#define MyAppVersion)website/frontend/src/pages/download.astro(version string)website/frontend/src/pages/index.astro(softwareVersionin JSON-LD)
Verify all 6 match by grepping for the version string across all files.
CHANGELOG
Update CHANGELOG.md with a new section for the version. Categorize changes as Added/Changed/Fixed.
Commit, tag, push
git add <changed files>
# Use -f for website/ files (gitignored)
git commit -m "vX.Y.Z: description"
git tag vX.Y.Z
git push && git push --tags
Wait for CI
Check build status: gh run list --limit 3
Wait for the Build & Release workflow to complete: gh run watch <run_id>
If build fails, check logs: gh run view <run_id> --log-failed
Deploy website (MANDATORY if download.astro or index.astro changed)
cd website/frontend && npx astro build && npx wrangler pages deploy dist --project-name clawbridge-site
If backend changed: cd website/backend && npx wrangler deploy
NOTE: npm run build runs astro check && astro build — the type checker has pre-existing errors in download.astro. Use npx astro build directly to skip type checking.
Post-deploy verification
- Check GitHub releases page has all artifacts
- Verify clawbridge.ai/download shows correct version
- Verify
curl -s http://127.0.0.1:8765/healthreturns the new version
Past failures to watch for
- v0.5.4: Website deploy was SKIPPED even though download.astro changed. Always deploy website when version files change.
- v0.5.5:
npm run buildfails due to pre-existing TS errors in download.astro. Usenpx astro builddirectly. - Python
\nin JS: When adding JS regexes in Python strings, use\\nnot\n. The\nbecomes a literal newline that breaks the<script>block. - Installer filename: Must always be
ClawBridge-Setup.exe— no version suffix. - v0.5.5:
--host 127.0.0.1is NOT a valid OpenClaw flag. Use--bind loopbackinstead. The wrong flag silently kills the gateway, causing 30s timeouts on every chat task. - OpenClaw gateway flags: Full command is
openclaw gateway --port 18789 --bind loopback --allow-unconfigured --auth none --dev. Always test gateway startup after changes.
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 · 67 lines · 0 tokens per session scan A 000b288c8362
deploy is a command published in the GitHub repository NickRomanek/clawbridge (23 stars, last pushed 7mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 752 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
ship
Deploy feature through automated staging validation to production with rollback testing.
ci
Run CI validation, create PRs, and merge on green.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
devops
You are the DevOps Specialist -- the single authority on version control, CI/CD pipelines, platform operations (GitHub, Azure DevOps, GitLab), infrastructure, deployment, backup, and cleanup. If it touches git, pipelines, or production infrastructure, it's yours.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.