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 executegit 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/execute)<a href="https://agentmods.dev/skills/0xmariowu/builders-dont-cry/execute"><img src="https://agentmods.dev/badge/skills/0xmariowu/builders-dont-cry/execute.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.00079 | $0.05215 |
| Opus 5 | $0.00039 | $0.02608 |
| Sonnet 5 | $0.00016 | $0.01043 |
| Haiku 4.5 | $0.00008 | $0.00522 |
Grade A, and why
execute 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 7d 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/execute — Let's fucking go: execute plan steps with dispatch + TDD loop
Step 0: Escape Hatch
If builder says 别走流程, 直接做, 简单点, or 不走地图, do not force /execute. 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.
Step 0.5: Project Goal Check
If PROJECT_GOAL.md exists in the target root, read it before execution. If the approved plan conflicts with current_phase, exit_criteria, or out_of_scope, stop and ask whether to update the goal or return to /plan. Do not edit PROJECT_GOAL.md automatically.
Contract
Each invocation:
- Find candidate plans via
bash ${BDC_HOME:-$HOME/.bdc}/scripts/active-plan-resolver.sh --list— resolver scans repo.bdc/plans/∪${BDC_HOME:-$HOME/.bdc}/plans/, applies INDEX-status / mtime / unfinished-checkbox filters. If multiple filesystem candidates appear, resolve from current-session evidence before asking: 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, use it and state the reason. Ask builder only when no unique candidate remains after session-context resolution, or when the next action is destructive/irreversible. - Read the plan header + the first unchecked
- [ ] Step - Look up
<role>in${BDC_HOME:-$HOME/.bdc}/standards/model-router.mdand dispatch accordingly - Run the verify command to collect evidence
- Pass → commit → change
- [ ]to- [x]in the plan → move to the next Step - Fail → root cause (
${BDC_HOME:-$HOME/.bdc}/standards/debugging.md) → retry once with the same role → if still failing, escalate to Opus or report to builder
Iron Law
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
Before claiming a Step is complete, in this message, you must have run the verify command and seen the output. These 6 excuses are all invalid:
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 227 lines · 79 tokens per session scan A 0e0675de5e65
execute is a skill published in the GitHub repository 0xmariowu/builders-dont-cry (4 stars, last pushed 4mo ago), licensed MIT. It adds 79 tokens to every session and 5,215 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…