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 plangit 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/plan)<a href="https://agentmods.dev/skills/0xmariowu/builders-dont-cry/plan"><img src="https://agentmods.dev/badge/skills/0xmariowu/builders-dont-cry/plan/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/plan"><img src="https://agentmods.dev/badge/skills/0xmariowu/builders-dont-cry/plan.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.00122 | $0.03412 |
| Opus 5 | $0.00061 | $0.01706 |
| Sonnet 5 | $0.00024 | $0.00682 |
| Haiku 4.5 | $0.00012 | $0.00341 |
Grade A, and why
plan 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 10d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/plan — Persist a structured plan
Step 0: Escape Hatch
If builder says 别走流程, 直接做, 简单点, or 不走地图, do not force /plan. 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 current project root, read it before writing the plan. If the request conflicts with current_phase, exit_criteria, or out_of_scope, stop and ask whether to update the goal or narrow the request. Do not edit PROJECT_GOAL.md automatically.
Contract
Each invocation produces one .bdc/plans/<proj>-<MMDD>-<topic>.md in the format specified by ${BDC_HOME:-$HOME/.bdc}/standards/plan-management.md (exec-plan + 7 role labels + atomic granularity), and spawns a reviewer to review the plan.
Use /plan when the work has any planning trigger: 3+ steps, cross-module changes, non-binary success criteria, or interface contract changes. Create the plan even if the user did not explicitly ask for one.
Prerequisites
Read once: ${BDC_HOME:-$HOME/.bdc}/standards/plan-management.md (format + 8 rules) + ${BDC_HOME:-$HOME/.bdc}/standards/model-router.md (role definitions) + ${BDC_HOME:-$HOME/.bdc}/standards/first-principles.md (constraint pass for non-trivial plans). Do not copy rules into the plan — reference them.
6-Step Process
1. Positioning (CLAUDE.md § Planning Discipline step 0)
One sentence: what is this? Let builder confirm. If unstable, stop and ask — do not drill into details.
2. Challenge premise
State what you believe the problem to be + why you believe that. Is this actually the right problem?
3. Prior-art check (CLAUDE.md north star + Planning Discipline step 2)
Use configured prior-art sources:
- configured local notes, docs, or knowledge tools when the builder has explicitly set them up
- current repo search with
rg,find, and source reads - relevant project docs such as README, architecture notes, ADRs, plans, or issue references
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.
- 10d ago First seen · 191 lines · 122 tokens per session scan A 1faf3650ef90
plan is a skill published in the GitHub repository 0xmariowu/builders-dont-cry (4 stars, last pushed 4mo ago), licensed MIT. It adds 122 tokens to every session and 3,412 once invoked, about $0.0006 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.
remove
Remove a deployed framework or addon from the current workspace.