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/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-doctor)<a href="https://agentmods.dev/commands/bar181/bar-observatory/bar-doctor"><img src="https://agentmods.dev/badge/commands/bar181/bar-observatory/bar-doctor/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/bar181/bar-observatory/bar-doctor"><img src="https://agentmods.dev/badge/commands/bar181/bar-observatory/bar-doctor.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.00022 | $0.00177 |
| Opus 5 | $0.00011 | $0.00088 |
| Sonnet 5 | $0.00004 | $0.00035 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
bar-doctor 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 9d 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
Run BAR Observatory's live diagnostic — distinct from the deterministic report, this answers "is the recorder healthy right now?" not "what happened in this session?"
- Determine the database path from
$ARGUMENTS, defaulting to.bar/ambient.sqlite. If no database has been initialized yet, runbar doctorwith no argument — it still reports on thebarbinary itself. - Run:
bar doctor <db> - Summarize the result plainly: which checks passed, which warned, and — critically — which capture channels actually have rows versus which are honestly reported as not recorded. Never round a warning up to "everything's fine."
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.
- 9d ago First seen · 17 lines · 22 tokens per session scan A 7dc9a119853f
bar-doctor is a command published in the GitHub repository bar181/bar-observatory (22 stars, last pushed 12d ago), licensed MIT. It adds 22 tokens to every session and 177 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
guide
Ask the plugin about itself — what a config key does, how the plan gate grades, what the journal can prove — answered from its own docs with a citation for every claim, by the read-only guide agent.
sanitize
Scan working, staged, and historical publication content for private-project identifiers, paths, secrets, and private-source overlap.
command-template.claude
Command "command-template.claude" from Enovatr-Labs/SpecRoute, covering what this command does, implementation, inline shell commands the slash command runs, output and when to use.
status
Report the current state of the SpecRoute skeleton - which top-level dirs exist, which artifacts have been drafted, what's outstanding.
README
Drop your project's slash commands here. Each command is a flat .md file with YAML frontmatter and a body. Users invoke as / .
review-spec
Review a spec, PRD, or implementation plan for implementation-readiness. Usage - /review-spec.