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 agentmods add skills/lucasfcosta/backpressured/confignpx skills add lucasfcosta/backpressured --skill configgit 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/config)<a href="https://agentmods.dev/skills/lucasfcosta/backpressured/config"><img src="https://agentmods.dev/badge/skills/lucasfcosta/backpressured/config.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.00060 | $0.03906 |
| Opus 5 | $0.00030 | $0.01953 |
| Sonnet 5 | $0.00012 | $0.00781 |
| Haiku 4.5 | $0.00006 | $0.00391 |
Grade A, and why
backpressured-config 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 5d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backpressured — Config
Overview
This is the setup step for the backpressure loop, not the loop itself. Its job is to produce a good BACKPRESSURE.md (the file the [[backpressured]] loop reads as authoritative project customization) and to make sure the MCP servers that loop relies on are installed and healthy.
Run only when the user types /backpressured:config. Do not start it from a /goal, a "backpressure" mention, or your own initiative — that is what disable-model-invocation enforces, and you must honor it.
You detect, then confirm — never silently guess and write. The user owns every value that lands in BACKPRESSURE.md.
What you produce
- A
BACKPRESSURE.mdat the project root (created, or edited if one exists). - A verified Playwright MCP, plus any auxiliary MCP servers the user opts into, registered in the project's
.mcp.json.
Keep the user oriented
This is an interactive setup, so the user should always know what you're doing and why — but don't make them read your work. Give one short, high-level note per phase, framed as conclusions, not process:
- Do: "Scanning the project to find its lint, test, and run commands…" · "Found it — tests run with
pnpm test, the app starts viadocker compose up. Confirm or correct each below." · "Setting up the Linear MCP — you'll finish sign-in with/mcpafter." - Don't: paste raw file contents, list every path you grepped, narrate each tool call, or think out loud. Report what you concluded, not how you searched.
- Keep secrets,
.envcontents, and long command output out of the chat — refer to them, never echo them. - Present findings as a short, confirmable summary and ask in plain language; when you take an action (install an MCP, write the file), say what you did in one line.
Step 1 — Create or edit?
Check for BACKPRESSURE.md at the project root.
- Absent → create mode: run detection (Step 2) and build the file from scratch.
- Present → edit mode (this is also how you "refresh"): read it, summarize back to the user what it currently says, and ask what they want to change. Also re-run detection and the project survey to surface anything new since last time — added scripts, new CI jobs or hooks, new project skills, MCP servers — and offer those as additions. Then edit in place: change only what's new or what the user asks for, and never clobber sections they already approved.
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.
- 5d ago First seen · 160 lines · 60 tokens per session scan A b9bf62773360
backpressured-config is a skill published in the GitHub repository lucasfcosta/backpressured (63 stars, last pushed 3mo ago), licensed MIT. It adds 60 tokens to every session and 3,906 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-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-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…
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…