Borrowing it
Nothing to install: this file belongs to AltimateAI/altimate-code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AltimateAI/altimate-code/main/.claude/commands/bridge-guard.mdgit clone --depth 1 https://github.com/AltimateAI/altimate-codeWrote 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/altimateai/altimate-code/bridge-guard)<a href="https://agentmods.dev/commands/altimateai/altimate-code/bridge-guard"><img src="https://agentmods.dev/badge/commands/altimateai/altimate-code/bridge-guard/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/altimateai/altimate-code/bridge-guard"><img src="https://agentmods.dev/badge/commands/altimateai/altimate-code/bridge-guard.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.00062 | $0.04205 |
| Opus 5.5 | $0.00025 | $0.01682 |
| Sonnet 5.5 | $0.00012 | $0.00841 |
| Haiku 4.5 | $0.00006 | $0.00421 |
Grade A, and why
bridge-guard 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.
How it starts
The opening of the file, as written. The whole thing — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bridge Merge Audit
Run this after script/upstream/bridge-merge.ts (or any large upstream merge) produces a PR. Catches the regression classes that v1.4.0 shipped before we built the three-layer safety net (commits 3a6b59bdea + 13ba57f7f1).
Input
$ARGUMENTS = PR number, or empty to detect from current branch via gh pr view. Branch name typically upstream/merge-vX.Y.Z.
Why this skill exists
The v1.4.0 bridge merge shipped 16 user-impacting regressions across 30 files. Root cause: many altimate customizations were never wrapped in altimate_change markers, so the bridge merge tool — working as designed — overwrote them with upstream's version. The branding scan was too narrow to catch user-visible bare opencode strings; behavior patches (function calls, retry loops, default values) had no marker discipline at all.
This skill walks the auditor through every regression class we've actually seen, with the exact greps + code reads to detect each one. Treat the patterns as a checklist, not a suggestion — every item below was a real bug in v1.4.0 that reached the user before we caught it.
Step 0: Setup
git fetch origin
gh pr view --json number,title,headRefName,baseRefName,url
git checkout <merge-branch>
git status --short
If working tree is dirty, stop. Capture base SHA: BASE=$(git merge-base HEAD origin/main). The audit compares HEAD vs $BASE.
Step 1: Run the three-layer tooling check (mandatory, do this first)
bun run script/upstream/analyze.ts --branding --strict
bun run script/upstream/analyze.ts --require-markers --strict
bun run script/upstream/analyze.ts --markers --base main --strict
All three must pass before continuing. If --branding flags leaks: those are user-visible strings the broadened scan caught (yargs describe, console output, User-Agent, MCP client name, OIDC audience, etc.). Fix each before moving on.
If --require-markers flags missing markers: behavioral patches in known-vulnerable files were lost. Restore them or remove the file from config.requireMarkers if it no longer holds patches.
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 · 263 lines · 62 tokens per session scan A 9d73fdfe9d28
bridge-guard is a command published in the GitHub repository AltimateAI/altimate-code (813 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 4,205 once invoked, about $0.0002 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-30.
Other commands, from other repositories
commit
Please summarize your current changes, generate a commit message in English, then add and commit. Never include any AI tool or model as a Co-Author in commit messages. No Co-Authored-By lines referencing AI assistants.
pr
A guided command for preparing a GitHub Pull Request, which is a proposed set of repository changes for review and merging. It reads the branch history and changed files to draft the request.
code-review
Review the current branch changes for bugs and style issues.
pr-ready
Run the project's pre-commit review loop to determine whether the current branch is ready to push — lint, tests, parallel pr-review-toolkit agents plus an over-engineering audit, fix-and-re-run until convergence.
clean_gone
Cleans up all git branches marked as [gone] (branches that have been deleted on the remote but still exist locally), including removing associated worktrees.
hatch3r-pr-resolve
Read open PR comments, evaluate each against current code via the rigor contract, implement accepted findings, reply inline. Multi-platform.