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 autoloopgit 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/autoloop)<a href="https://agentmods.dev/skills/0xmariowu/builders-dont-cry/autoloop"><img src="https://agentmods.dev/badge/skills/0xmariowu/builders-dont-cry/autoloop/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/autoloop"><img src="https://agentmods.dev/badge/skills/0xmariowu/builders-dont-cry/autoloop.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.00040 | $0.01173 |
| Opus 5 | $0.00020 | $0.00587 |
| Sonnet 5 | $0.00008 | $0.00235 |
| Haiku 4.5 | $0.00004 | $0.00117 |
Grade A, and why
autoloop 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/autoloop
Step 0: Escape Hatch
If builder says 别走流程, 直接做, 简单点, or 不走地图, do not run /autoloop. Acknowledge once and do the smallest direct action.
Exception: the escape hatch does not bypass safety gates for destructive changes, secret access, public upload, deploy, database migration, force push, or irreversible writes.
Contract
/autoloop is an explicit automation wrapper for mature, already-approved plans.
It may run:
/execute -> /verify -> /ship
It must not create a plan, expand scope, choose new dependencies, perform destructive actions, push, open a PR, or publish unless the active plan and /ship both say that action is in scope and builder explicitly approves it.
Preconditions
Before doing anything else:
- Resolve the active plan:
bash ${BDC_HOME:-$HOME/.bdc}/scripts/active-plan-resolver.sh --single - Confirm the plan is reviewed or explicitly approved by builder.
- Confirm at least one unchecked step remains.
- Confirm the plan has executable verify commands.
- Confirm no step asks for destructive work without explicit owner approval.
If any precondition fails, stop and report the exact missing condition. Do not downgrade into ad-hoc /execute.
Process
- Run
/executeon the next unchecked step. - If
/executepasses, run/verifyon the finished work. - If
/verifyreturnsAPPROVE, continue until the next boundary or until no unchecked steps remain. - If
/verifyreturnsREQUEST_CHANGES, treat it as failure 1 and run one correction loop through/execute. - If the correction loop still fails, or any stage accumulates two failures, stop and run
/handoff. - When the plan has no unchecked steps, run
/shipfor local-first go/no-go. Do not push, publish, or open a PR unless/shipasks for it and builder confirms.
Failure Budget
| Event | Count |
|---|---|
/execute verify failure |
1 |
/verify REQUEST_CHANGES |
1 |
/ship NO-GO with actionable fix |
1 |
| Same stage fails again after one correction loop | stop |
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 · 120 lines · 40 tokens per session scan A 626f34905b23
autoloop is a skill published in the GitHub repository 0xmariowu/builders-dont-cry (4 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 1,173 once invoked, about $0.0002 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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
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…