setup

A guided setup for adding the standdown library to a browser extension and checking its conformance. The library helps an extension avoid taking affiliate credit when another partner already owns the sale.

In plain words
What is it for?
For installing standdown, selecting an adapter based on the extension’s permissions, placing checks at affiliate-attribution points, building the extension, and grading the integration.
Why use it?
It provides a prescribed installation and verification process, including a separate path for extensions that already have similar rules. It also keeps attribution decisions local and makes failures favor standing down.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/dupe-com/standdown/setup
Any agent
npx skills add dupe-com/standdown --skill setup
Clone the repo
git clone --depth 1 https://github.com/dupe-com/standdown

Made for: Claude Code, Codex.

Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 749 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00081 $0.00749
Opus 5 $0.00041 $0.00375
Sonnet 5 $0.00016 $0.00150
Haiku 4.5 $0.00008 $0.00075

Measured 2d ago against content hash 648a2fb8e8fe, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

setup 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.

skills/setup/SKILL.md · 52 lines

How it starts

The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.

standdown setup: install → integrate → grade

Thin router. AGENTS.md at the repo root is the source of truth for the greenfield integration loop — install, pick the adapter, gate every attribution firing point on decision.standDown, bundle, and grade with conformanceGrade. Do not summarize those steps from memory; read the file and follow it exactly, in order. (If the standdown repo isn't already local, fetch the raw file: https://raw.githubusercontent.com/dupe-com/standdown/main/AGENTS.md.)

What to do

  1. Confirm the branch first (AGENTS.md Step 0). If the extension ALREADY has its own stand-down / affiliate-attribution logic (a disable list, ignore_param/self-click handling, cookie or param stand-down checks, a FALLBACK_POLICY, or "stand down"/"suppress" code), this is brownfield — STOP and use the adopt skill (/standdown:adopt) / ADOPTING.md instead (shadow-mode migration, parity before cutover). Only proceed here for a greenfield install.

  2. Drive AGENTS.md Steps 1–6 in order against the user's extension: confirm the target, install, pick the adapter by permissions (never add webRequest/webNavigation to a published extension), integrate at the real activation site, bundle, then grade.

  3. Grade with conformanceGrade — the authoritative number (AGENTS.md Step 6): cd standdown/audit && npm install && DISABLE_HOSTS="<hosts you disable>" npx tsx grade/conformance.ts. Target A/A+; fix anything below A and re-grade. grade/grade.ts (the in-browser testext sensor) is optional and routinely reads C (inert) on real host extensions — do not report it as the grade.

Rules

  • Never break the invariants: decisions stay local and synchronous (no network in the decision path), signals exclude user identity, everything fails toward standing down.
  • Confirm context before editing, and report what changed (adapter, gated files, build command, final grade) at the end.
  • Don't restate AGENTS.md here — if it and this file ever disagree, AGENTS.md wins; fix the drift rather than following the stale copy.

Read the full file on GitHub · 52 lines

Changes

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.

  1. 2d ago First seen · 52 lines · 81 tokens per session scan A 648a2fb8e8fe

Subscribe to this mod's changes

setup is a skill published in the GitHub repository dupe-com/standdown (5 stars, last pushed 20d ago), licensed MIT. It adds 81 tokens to every session and 749 once invoked, about $0.0004 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.

Related

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…

ericrisco/rsc-harness · 76 tokens

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"…

Gingg7260/affiliate-skills · 103 tokens

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…

Gingg7260/affiliate-skills · 87 tokens

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"…

Gingg7260/affiliate-skills · 87 tokens

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…

Gingg7260/affiliate-skills · 87 tokens

skill-finder

Find the right Affitor skill for your goal. Triggers on: "which skill should I use", "find me a skill", "what skills are available", "help me choose a skill", "skill for SEO", "skill for email", "explore skills", "I'm new to Affitor", "what can Affitor do", "search skills", "skill for blog writing", "skill for landing…

Gingg7260/affiliate-skills · 94 tokens