Skip to content

What Bravos is made of

Bravos is a CLI and a set of skills. The work is done by four tools, through the coding agent in your session.

Tool What it does Where it comes from Plan
guardlink the threat model as annotations, its lint gate, and the hypothesis ledger npm, npm install -g guardlink Free
cxg pentests as code: templates run against an authorized target released binary or crate Free
The code graph, codegraph-build and codegraph-mcp routes, callers, reach and blast radius, joined to the threat model bravos setup, through your licence Team
The SAST analyzer, bravos-cli Semgrep rules, taint over the graph, dependency advisories, secrets and IaC bravos setup, through your licence Team

bravos setup --tools -y installs guardlink 2.7.1 and cxg 1.9.2 through npm and cargo. Bravos drives the real guardlink and cxg CLIs and bundles no copy of either, so their own docs on this site apply as written.

Path What it is
.claude/skills/bravos*/, .agents/skills/bravos*/ the 16 skills, for Claude Code and for Codex and the agents sharing its folder
.claude/skills/guardlink-*/, .agents/skills/guardlink-*/ guardlink’s playbook skills
.bravos/hooks/ the session-start briefing, the coach, threat cards, and the pre-PR gate and autopilot when turned on
.claude/settings.json, .codex/hooks.json, .cursor/hooks.json, .agents/hooks.json the hook registrations
.mcp.json, .codex/config.toml, opencode.json MCP servers: guardlink, cxg and the code graph
.opencode/, .omp/, .cursor/rules/bravos.mdc the opencode commands and plugin, the omp extension, the Cursor pointer
.bravos/context/ your design documents, when you add any
.bravos/setup.json, .bravos/skills.lock the repository’s setup answers, and the sha256 of every file Bravos wrote
.github/workflows/bravos-*.yml the PR gate and nightly, with --ci

Only the selected agents receive their integration files when --agent is explicit. These files are meant to be committed; see Share Bravos with your team. bravos uninstall removes what it wrote and has not been edited.

~/.bravos, or $BRAVOS_HOME, holds the licence, the staged analyzer and code graph, the graph store and the workspace registry.

  • No Bravos server. The threat model is in your repository and git is how a team shares it. The graph uses a local store; runs, receipts and reports are local files, not a central Bravos service.
  • No orchestrator. Bravos never spawns another agent CLI. The agent you opened does the work.
  • Local licence verification. The licence is checked on the machine, with signature verification locally. Signed-in machines also renew device licences. See how licensing works.

The Python bravos (0.x) had a self-hosted server, a CI runner image and a terminal UI. The npm CLI has none of them. bravos watch is the live view, and git is the shared record. If an old Python bravos comes first on your PATH, rename it or remove it with pipx or uv, so bravos means this CLI. bravos doctor lists old Python bravos skills left in your user skill folders.