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/dupe-com/standdown/adoptnpx skills add dupe-com/standdown --skill adoptgit clone --depth 1 https://github.com/dupe-com/standdownWhat 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.00115 | $0.00842 |
| Opus 5 | $0.00057 | $0.00421 |
| Sonnet 5 | $0.00023 | $0.00168 |
| Haiku 4.5 | $0.00012 | $0.00084 |
Grade A, and why
adopt 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 2d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
adopt-standdown: brownfield migration onto standdown
ADOPTING.md at the repo root is the source of truth. This skill is a thin
router that walks the agent through its five phases and enforces the one
non-negotiable: shadow-observe and reconcile before you cut over — never
big-bang-replace revenue-critical stand-down logic.
First, confirm this is a brownfield case: the target already stands down
today (Phase 1 grep will show disable_domains, ignore_param, cookie/param
checks, a fetched/fallback policy, or "stand down"/"suppress" code). If it has
none, stop and use the greenfield setup skill (/standdown:setup) instead.
Then read ADOPTING.md and drive its phases in order. Do not summarize from
memory — the detail (grep table, mapping table, invariant constraints, worked
Dupe example) lives there.
- DETECT — grep the whole repo (background worker, content scripts, and any policy-serving server) and build the detection inventory: one row per rule with network/merchant, exact current behavior, file:line, and any TTL.
- MAP — translate each row to exactly one
standdownconcept via the mapping table (params→landingParams, cookies→cookiePatternsname-only, merchant blocks→disableHosts, own attribution→selfPatterns+selfExemptionScope). Match current fleet behavior, not the full library. - SHADOW — baseline grade → observe-only beside the real path (namespaced shadow key / analytics, no action taken) → reconcile every divergence (safe-stricter / dangerous-more-permissive / needs-human-decision) → flagged cutover (off-by-default) → delete old code last.
- GUARD — hold the invariants as hard constraints: no network call in the decision path (I1), fail toward standing down (I3), monotone/never lift an active stand-down (I4), cookie NAMES only (I2).
- VERIFY — characterization tests, audit grade ≥ baseline, no-fail-open assertions, flag off by default, old code retained as rollback.
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.
- 2d ago First seen · 57 lines · 115 tokens per session scan A 328f7b3d9022
adopt is a skill published in the GitHub repository dupe-com/standdown (5 stars, last pushed 20d ago), licensed MIT. It adds 115 tokens to every session and 842 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
chrome-extension
Use when building or shipping a Manifest V3 browser extension and hitting its quirks — service worker dying and losing state, permission warnings, a Chrome Web Store rejection, content-script/worker/popup messaging, or an MV2-to-V3 migration. NOT a generic web app (that is nextjs), NOT a desktop shell (that is…
browser-extension-patterns
Build browser extensions with Manifest V3 for Chrome, Firefox, and cross-browser compatibility. Covers content scripts, background workers, popup UI, storage APIs, and extension messaging. Triggers on browser extension development, Manifest V3, or Chrome extension requests.
category-designer
Define a new category where your product wins by default. Reframe the buying decision. Triggers on: "create a category", "category design", "define my category", "category of one", "reframe the market", "position as category king", "new category", "category creation", "own a category", "category strategy"…
compliance-checker
Check affiliate content for FTC compliance and platform rules. Triggers on: "check my content for compliance", "FTC disclosure check", "is this legal", "review for compliance", "check affiliate disclosure", "am I FTC compliant", "audit my content", "compliance review", "legal check", "platform rules check", "check…
self-improver
Review affiliate campaign results and improve strategy. Triggers on: "review my results", "what went wrong", "how to improve conversions", "analyze my campaign", "affiliate retrospective", "why am I not converting", "improve my strategy", "what should I change", "campaign review", "optimize my approach", "learn from…
funnel-planner
Plan a complete affiliate funnel from research to revenue. Triggers on: "plan my affiliate funnel", "create a funnel strategy", "affiliate business plan", "how to start affiliate marketing", "full funnel roadmap", "plan from scratch", "week by week affiliate plan", "chain skills together", "build my funnel"…