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/mcwalrus/oppertunity-party/backpressurenpx skills add mcwalrus/oppertunity-party --skill backpressuregit clone --depth 1 https://github.com/mcwalrus/oppertunity-partyWrote 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/mcwalrus/oppertunity-party/backpressure)<a href="https://agentmods.dev/skills/mcwalrus/oppertunity-party/backpressure"><img src="https://agentmods.dev/badge/skills/mcwalrus/oppertunity-party/backpressure.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 | $0.00138 | $0.02581 |
| Opus 5 | $0.00069 | $0.01290 |
| Sonnet 5 | $0.00028 | $0.00516 |
| Haiku 4.5 | $0.00014 | $0.00258 |
Grade C, and why
backpressure scanned grade C 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 3d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
(`rm -rf .docker/volumes/`) and isolated test databases serve this purpose. How it starts
The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Backpressure
What Backpressure Means Here
In agent-driven development, backpressure is the resistance signal that tells an agent its output was wrong and exactly how to fix it. The term is borrowed deliberately: just as hydraulic backpressure resists flow until upstream pressure builds to push through, a well-designed feedback system resists bad output until the agent corrects it.
Your backpressure as an engineer is finite. Every time you type a message telling an agent it missed an import, forgot a semicolon, or broke a layout, you are spending it. That is time taken away from architecture, judgment, and problems machines cannot solve. Any feedback a machine can generate automatically is feedback you should never be giving manually.
The central question to ask about any agent workflow: am I wasting my backpressure?
The Four Properties of Good Backpressure
Feedback signals that work share these properties. Use them to evaluate any check in your pipeline:
| Property | What it means | What bad looks like |
|---|---|---|
| Automated | Generated by a machine, not you | You are typing the same correction more than once |
| Immediate | Fires at the moment of the mistake, not later | Agent commits broken code; you catch it on review |
| Specific | Names the file, line, and reason | "Build failed" with no further detail |
| Actionable | The agent can fix it without asking you | Vague lint warnings the agent ignores |
When a check fails all four, remove it or improve it. A check that is automated but not specific (e.g. "tests failed" with no output) is worse than useless — it consumes the agent's context without providing a path forward.
Backpressure Layers
Think in layers. Each layer catches a different class of mistake. The goal is full coverage with no gaps that require you to fill in manually.
Layer 1: Compiler / Type System
The fastest and cheapest feedback. Fires before any code runs.
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.
- 3d ago First seen · 231 lines · 138 tokens per session scan C 7fca94d24a28
backpressure is a skill published in the GitHub repository mcwalrus/oppertunity-party (0 stars, last pushed 11d ago), licensed MIT. It adds 138 tokens to every session and 2,581 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
emdash-cli
Use the EmDash CLI to manage content, schema, media, and more. Use this skill when you need to interact with a running EmDash instance from the command line — creating content, managing collections, uploading media, generating types, or scripting CMS operations.
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
cocoindex-diagrams
This skill should be used when creating, editing, or reviewing inline SVG diagrams for the CocoIndex docs site (anything under docs/src/content/docs/). It encodes the component-based primitive system under docs/src/components/diagrams/, the palette + shape semantics, the preview-and-verify loop using headless Chrome…
investigate
Investigate a single EmDash issue end to end -- classify, choose a repro path, reproduce, diagnose, verify, and (only on an explicit maintainer fix directive) fix and confirm. Every verdict carries its evidence.
dagster-docs
Expert guidance for writing documentation for the Dagster docs website. ALWAYS use before creating or updating documentation in the docs directory.
repro-public
Reproduce a bug in the public-facing rendered site (not the admin). Attach a container, start the demo dev server, drive public routes with agent-browser, and capture the reproduction as screenshots plus a replayable transcript.