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 lucasfcosta/backpressured --skill goalgit clone --depth 1 https://github.com/lucasfcosta/backpressuredWrote 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/lucasfcosta/backpressured/goal)<a href="https://agentmods.dev/skills/lucasfcosta/backpressured/goal"><img src="https://agentmods.dev/badge/skills/lucasfcosta/backpressured/goal.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.00095 | $0.03216 |
| Opus 5 | $0.00048 | $0.01608 |
| Sonnet 5 | $0.00019 | $0.00643 |
| Haiku 4.5 | $0.00010 | $0.00322 |
Grade A, and why
backpressured scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
"Run for real: curl, browser, full suite, full benchmarks, holistic independent review" [shape=box]; How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backpressured
Overview
You are the producer's backpressure of LAST resort — your job is to replace yourself with machines that say "no" first. A human reading your code should be the last line of defense, never the first. Every "no" a machine can produce — a failing test, a type error, a lint rule, a benchmark regression, a reviewer's objection — must be produced by the machine, before you hand anything back.
So you do not stop when the code "works." You drive the goal through the full loop below and stop only when every acceptance criterion and every quality check passes — or when you are genuinely blocked and can name exactly what is blocking you.
When to Use
- The user explicitly mentions "backpressured" or "backpressure" — asking for a backpressured loop/run, "do this backpressured", or invoking it by that name (brand-name mentions count too).
- The user runs the
/backpressured:goalcommand.
Not for: generic "implement X", "fix this bug", "build X and ship it", "open a PR", or a bare /goal request that does not explicitly mention backpressure. A finished, landed result being expected is not by itself enough — wait for one of the two signals above. Also not for one-line factual answers, pure research/exploration, or when the human wants to drive step by step.
First: pin down "done"
"Done" is defined by criteria, so make them explicit before anything else:
- Acceptance criteria — what must be true for the goal to be met. If the user didn't list them, infer them and state them up front.
- Quality checks — lint, tests, new behavior covered, project verification scripts, benchmarks, review. These apply on top of acceptance criteria, every time.
- Project customization — check for an optional
BACKPRESSURE.mdat the project root and fold its instructions in now (see Figuring out the checks).
The Loop
digraph backpressure_loop {
"Goal received" [shape=doublecircle];
"Write lightweight plan (approach + architecture, not details)" [shape=box];
"Independent reviewer approves the plan?" [shape=diamond];
"Revise plan" [shape=box];
"Write the next patch" [shape=box];
"Run every applicable check (incl. independent code review)" [shape=box];
"All checks green?" [shape=diamond];
"Fix the failure" [shape=box];
"Genuinely blocked?" [shape=diamond];
"STOP: name the blocker, do NOT mark done" [shape=octagon, style=filled, fillcolor=red, fontcolor=white];
"All acceptance + quality criteria met?" [shape=diamond];
"Run for real: curl, browser, full suite, full benchmarks, holistic independent review" [shape=box];
"Open the PR" [shape=box];
"Monitor: CI, comments, conflicts" [shape=box];
"Landed clean with nothing outstanding?" [shape=diamond];
"Done" [shape=doublecircle];
"Goal received" -> "Write lightweight plan (approach + architecture, not details)";
"Write lightweight plan (approach + architecture, not details)" -> "Independent reviewer approves the plan?";
"Independent reviewer approves the plan?" -> "Revise plan" [label="no"];
"Revise plan" -> "Independent reviewer approves the plan?";
"Independent reviewer approves the plan?" -> "Write the next patch" [label="yes"];
"Write the next patch" -> "Run every applicable check (incl. independent code review)";
"Run every applicable check (incl. independent code review)" -> "All checks green?";
"All checks green?" -> "Fix the failure" [label="no"];
"Fix the failure" -> "Genuinely blocked?";
"Genuinely blocked?" -> "STOP: name the blocker, do NOT mark done" [label="yes"];
"Genuinely blocked?" -> "Run every applicable check (incl. independent code review)" [label="no"];
"All checks green?" -> "All acceptance + quality criteria met?" [label="yes"];
"All acceptance + quality criteria met?" -> "Write the next patch" [label="no — keep going, do NOT hand back"];
"All acceptance + quality criteria met?" -> "Run for real: curl, browser, full suite, full benchmarks, holistic independent review" [label="yes"];
"Run for real: curl, browser, full suite, full benchmarks, holistic independent review" -> "Open the PR";
"Open the PR" -> "Monitor: CI, comments, conflicts";
"Monitor: CI, comments, conflicts" -> "Landed clean with nothing outstanding?";
"Landed clean with nothing outstanding?" -> "Write the next patch" [label="no"];
"Landed clean with nothing outstanding?" -> "Done" [label="yes"];
}
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 · 158 lines · 95 tokens per session scan A 9e9e070f976a
backpressured is a skill published in the GitHub repository lucasfcosta/backpressured (63 stars, last pushed 3mo ago), licensed MIT. It adds 95 tokens to every session and 3,216 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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…