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.
npx agentmods add commands/bar181/bar-observatory/bar-initgit clone --depth 1 https://github.com/bar181/bar-observatoryWrote 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/bar181/bar-observatory/bar-init)<a href="https://agentmods.dev/commands/bar181/bar-observatory/bar-init"><img src="https://agentmods.dev/badge/commands/bar181/bar-observatory/bar-init.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 | $0.00020 | $0.00359 |
| Opus 5 | $0.00010 | $0.00179 |
| Sonnet 5 | $0.00004 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
bar-init 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 4d 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
$ARGUMENTS
Set up BAR Observatory in the current project. This is the first command to run — everything
else (/bar-report, /bar-interpret, /bar-doctor, /bar-query, and the plugin's own hooks/MCP
server) reads and writes the .bar/ directory this creates.
- Determine the target directory from
$ARGUMENTS(a path), defaulting to.(the current project root — the directory the.barfolder should live under so the plugin's hooks andbar-mcp --db-root .barfind it with zero extra configuration). - Run:
bar init --dir <dir> - This is idempotent — safe to run again on an existing project, it never overwrites a
config that's already there ("Kept" instead of "Created" on a second run). Report exactly what
it did (created vs. kept) and where:
.bar/config.toml,.bar/ambient.sqlite,.bar/index.sqlite. - If
barisn't found on PATH, tell the user to runcargo install bar-observatoryfirst (andcargo install bar-hook bar-mcptoo, for the plugin's hooks and MCP server to actually capture anything — see this repo's README for why those resolve via PATH today). - Once init succeeds, tell the user their next step: run a real Claude Code task/session (the
plugin's hooks capture it automatically from here on), then
/bar-reportto see it.
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.
- 4d ago First seen · 24 lines · 20 tokens per session scan A 27989ad7f932
bar-init is a command published in the GitHub repository bar181/bar-observatory (22 stars, last pushed 7d ago), licensed MIT. It adds 20 tokens to every session and 359 once invoked, about $0.0001 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-30.
Other commands, from other repositories
spec
Generate a specification for AI-assisted implementation.
ticket
Take a GitHub issue through an isolated implementation and pull request in its own Herdr tab.
krait-poc
Write and run a valid Foundry proof-of-concept that proves (or disproves) a Solidity exploit by asserting the actual harm on a forked chain or against local source.
usage
Audit pipeline: token spend attributed by phase, task, model, author and time — with cache economics, cost-per-task and a usage trend. Read-only (never mutates the manifest).
krait-review
Re-examine findings killed by the Critic's automatic gates. Catches over-filtering without compromising the main report's zero-FP standard.
report
Produce executive and technical compliance reports.