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/beevibe-ai/beevibe-ctoWrote 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/beevibe-ai/beevibe-cto/discover)<a href="https://agentmods.dev/commands/beevibe-ai/beevibe-cto/discover"><img src="https://agentmods.dev/badge/commands/beevibe-ai/beevibe-cto/discover.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.1 | $0.00058 | $0.00502 |
| Opus 5 | $0.00029 | $0.00251 |
| Sonnet 5 | $0.00012 | $0.00100 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
discover 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 8d 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
/adr:discover — Repo scan and PRD draft
Use when the user wants the cheap, fast preview: "what does ADR think about my repo?", "draft a PRD I can edit", "what patterns are in this codebase?".
Step 1 — Confirm the decision name
Ask the user (skip if they already named it):
What architecture decision is the PRD for? (e.g. "event bus topology", "retrieval architecture")
Capture as <DECISION>.
Step 2 — Check the environment
npx -y --package=github:beevibe-ai/beevibe-cto adr-doctor
adr discover only needs an LLM provider (no web search). If that one is missing, invoke /adr:doctor to set it up.
Step 3 — Run discover via the MCP server
Use the adr_discover MCP tool:
{
"repo_path": ".",
"decision": "<DECISION>",
"out_dir": ".adr-runs/<slug>-discover"
}
Runs in 15–60 seconds and costs under a cent on gpt-4.1-mini.
Step 4 — Show the user the artifacts
The tool response gives you pattern_count, antipattern_count, and the path to pdr.draft.md. Read pdr.draft.md and show the user:
- The 3 most interesting patterns (with their file:line citations)
- The 2 most interesting anti-patterns (with their reasons)
- The Open questions section, verbatim — these are what the user must fill in before deep-research
Step 5 — Offer next steps
- Edit
pdr.draft.mdto fill in Open questions, then run/adr:decide(which will use the draft as input via--input-path) - Run
/adr:decidedirectly withdiscover_first: trueand let it skip the manual review step - Pipe the draft into a GitHub issue comment (for the bot workflow)
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.
- 8d ago First seen · 52 lines · 58 tokens per session scan A f97d627e89f4
discover is a command published in the GitHub repository beevibe-ai/beevibe-cto (105 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 58 tokens to every session and 502 once invoked, about $0.0003 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
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
advanced-code-review-context
Advanced Code Review Phase 2: Context Analysis - load previous reviews, PR history, declined items.
code-review-give
Give mode for code-review: Review someone else's code with multi-pass analysis and structured recommendations.
pr-distill
Analyze a PR and generate a review distillation report that categorizes changes by review necessity.
review-design-verify
Phases 4-5 of reviewing-design-docs: Interface Verification + Implementation Simulation.
mach12:issue-review
Read a GitHub issue and all comments, review the implementation plan, and present findings.