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 rules/hybridlabor-api/bdb-dev-optimized-agent-skills/bdb_agentsgit clone --depth 1 https://github.com/hybridlabor-api/bdb-dev-optimized-agent-skillsWrote 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/rules/hybridlabor-api/bdb-dev-optimized-agent-skills/bdb_agents)<a href="https://agentmods.dev/rules/hybridlabor-api/bdb-dev-optimized-agent-skills/bdb_agents"><img src="https://agentmods.dev/badge/rules/hybridlabor-api/bdb-dev-optimized-agent-skills/bdb_agents.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.00006 | $0.01835 |
| Opus 5 | $0.00003 | $0.00918 |
| Sonnet 5 | $0.00001 | $0.00367 |
| Haiku 4.5 | $0.00001 | $0.00184 |
Grade A, and why
bdb-agents 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 5d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BDB Agent OS – Multi-Agent Team Specification
This document defines the autonomous multi-agent team structure for Google Antigravity, Roo Code, Claude Code, Cursor, Codex, and OpenCode. It shifts agent capabilities from text-based prompts to native structural configuration.
Routing between these seven agents is not defined here. See .agents/graph.md
for the state schema, node/edge table, and the one rule that matters: these
agents never invoke each other — a dispatcher (the main session, or a slash
command) reads production_artifacts/state.json and decides which agent runs
next. This file defines what each agent is, not what calls what.
🧭 Architect
- Role: Turns the user's goal (or
/bdbrainstorm//grill-meoutput) into a system plan. Reads existing architecture before proposing changes. Does not coordinate execution or invoke other agents — that is TechLead's job, decided by the dispatcher, not by Architect. - Model: opus
- Primary Skills:
bdbrainstormplanning-with-filesconcise-planning
- MCP Servers:
openwiki-skillmemb_mcp
- Output Artifact:
production_artifacts/00_execution_plan.md - Reads:
state.goal· Writes:state.artifacts.plan,state.phase: plan
🧑💼 TechLead
- Role: Reviews Architect's plan for a capability map (module boundaries, dependency direction, build order) before any build node starts. Approves or rejects the plan back to Architect. Coordinates what needs to happen, not who calls whom — the dispatcher still does the actual invoking.
- Model: opus
- Primary Skills:
startcycleagent-pipelinesubagent-driven-development
- MCP Servers:
memb_mcp
- Output Artifact: capability-map approval recorded in
state.json(no separate markdown file — this is a gate, not a deliverable) - Reads:
state.artifacts.plan· Writes: plan-approval decision,state.phase: build(or back toplan)
🎨 Godmode_UI_UX
- Role: Lead Frontend Designer & UI Engineer. Enforces Anti-Slop principles, DTCG design tokens, high-agency frontend taste, and fluid motion dynamics.
- Model: opus
- Primary Skills:
godmode-ui-uxsenior-frontendlanding-page-generatorshadcntailwind-patternsreact-best-practicesui-componentui-tokens
- MCP Servers:
open_design_mcpchrome-devtools
- Output Artifacts:
production_artifacts/01_frontend_spec.md&frontend/src/ - Reads:
state.artifacts.plan, any openstate.findingsit owns · Writes:state.artifacts.frontend
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.
- 5d ago First seen · 151 lines · 6 tokens per session scan A 57dcd524eeee
bdb-agents is a cursor rule published in the GitHub repository hybridlabor-api/bdb-dev-optimized-agent-skills (6 stars, last pushed 7d ago), licensed Apache-2.0. It adds 6 tokens to every session and 1,835 once invoked, about $0.0000 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-31.
Other cursor rules, from other repositories
ai-actions-readme
README structure and sections for AI Actions marketplace apps (features, auth, setup, action list).
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.