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 skills add 0xmariowu/builders-dont-cry --skill using-bdcgit clone --depth 1 https://github.com/0xmariowu/builders-dont-cryWrote 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/skills/0xmariowu/builders-dont-cry/using-bdc)<a href="https://agentmods.dev/skills/0xmariowu/builders-dont-cry/using-bdc"><img src="https://agentmods.dev/badge/skills/0xmariowu/builders-dont-cry/using-bdc/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/skills/0xmariowu/builders-dont-cry/using-bdc"><img src="https://agentmods.dev/badge/skills/0xmariowu/builders-dont-cry/using-bdc.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.00051 | $0.00922 |
| Opus 5 | $0.00026 | $0.00461 |
| Sonnet 5 | $0.00010 | $0.00184 |
| Haiku 4.5 | $0.00005 | $0.00092 |
Grade A, and why
using-bdc 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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
using-bdc
Orient a fresh session to the local BDC without becoming a broad automatic hook.
Do not wire this skill into UserPromptSubmit. Because: it is an orientation skill for choosing a BDC route, not a broad automatic hook.
Step 0: Escape Hatch
If builder says 别走流程, 直接做, 简单点, or 不走地图, do not route into the BDC map. Acknowledge once and do the smallest direct action.
Exception: do not bypass safety gates for destructive changes, secret access, public upload, deploy, database migration, force push, or irreversible writes.
Roadmap
/idea -> /plan -> /execute -> /verify -> /ship
Use ${BDC_HOME:-$HOME/.bdc}/standards/roadmap.md as the source of truth for the five-station map. /autoloop is an explicit automation wrapper, not a sixth station.
Use ${BDC_HOME:-$HOME/.bdc}/standards/route-intent.md as the source of truth for natural-language routing, escape directives, meta questions, and high-risk false-positive routes.
Route
| User intent | Route |
|---|---|
| Clarify a fuzzy idea before planning | /idea |
| Need a written plan | plan |
| Start executing an approved plan | execute |
| Review completed work independently | /verify |
| Decide whether work is ready to ship | /ship |
| Explicitly automate an approved plan | /autoloop |
| Continue from prior work | pickup or handoff |
| Watch pull request or GitHub events | watch-pr |
| Graph or query local knowledge | Out of BDC core |
| Check BDC health | /health or ${BDC_HOME:-$HOME/.bdc}/bin/bdc doctor |
| Need standards map | ${BDC_HOME:-$HOME/.bdc}/standards/dispatch.md |
Active plan check
If the user says "start", "开始", "go", or "执行", first check whether an active plan exists:
bash ${BDC_HOME:-$HOME/.bdc}/scripts/active-plan-resolver.sh --list
If exactly one active plan is selected, route to /execute. If multiple filesystem candidates appear, first resolve from current-session evidence: explicit plan path/name in the prompt, the plan just created/reviewed/approved in this session, a current-plan cursor if present, current repo target root, or a clear project/topic match. If one candidate is uniquely supported, route to /execute and state the reason. Do not ask builder solely because the resolver returned multiple stale active plans; ask only when no unique candidate remains after context resolution, or when the next action is destructive/irreversible.
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 · 76 lines · 51 tokens per session scan A 00c3b631c727
using-bdc is a skill published in the GitHub repository 0xmariowu/builders-dont-cry (4 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 922 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.