Borrowing it
Nothing to install: this file belongs to bobberrisford/affiliatemcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bobberrisford/affiliatemcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/bobberrisford/affiliatemcpWrote 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/instructions/bobberrisford/affiliatemcp/claude-md)<a href="https://agentmods.dev/instructions/bobberrisford/affiliatemcp/claude-md"><img src="https://agentmods.dev/badge/instructions/bobberrisford/affiliatemcp/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/bobberrisford/affiliatemcp/claude-md"><img src="https://agentmods.dev/badge/instructions/bobberrisford/affiliatemcp/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.00376 | $0.00376 |
| Opus 5 | $0.00188 | $0.00188 |
| Sonnet 5 | $0.00075 | $0.00075 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
affiliatemcp CLAUDE.md 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 10d 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.
What it actually says
Claude Code project instructions
@AGENTS.md
Use the repo-local delivery-steward skill for implementation and delivery,
prepare-for-review for PR handoff, and review-pr for independent review.
For multi-PR work, write the dependency graph and risk gates before coding.
Do not build production foundations or child implementation PRs ahead of an
unresolved decision, even as drafts; discovery and explicitly disposable
prototypes are allowed. Keep the maintainer risk-review lane to one PR and use
at most two routine lanes for decision-complete work in disjoint domains. Make
safe scoped corrections and validate them directly instead of handing routine
work back. Do not request @offmann; Rob is the current maintainer decision
owner. For Rob-authored risk PRs, use an independent agent review plus green CI
as the default backstop, then let Rob deliberately accept or reject the risk.
Never merge unless Rob or another maintainer explicitly asks you to merge that
specific PR.
When an interaction reveals a concrete delivery-system lesson, include a brief
optional side note with evidence and a proposed improvement; stay silent when
there is no meaningful lesson and keep governance edits out of feature PRs.
Multi-PR features
A feature too big for one coherent PR ships as multiple linked PRs, never one mega-PR. Before coding, write the workstream brief (user outcome, dependency graph, owning domains, risk gates, acceptance proof per PR, stop conditions) in the first PR or a tracking issue. Land in dependency order: decision PR for unresolved governance or contracts first, then the smallest foundation with its first real consumer, then stacked vertical slices, then integration proof. See AGENTS.md ("For a feature that needs multiple PRs…") for the full protocol.
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.
- 10d ago First seen · 31 lines · 376 tokens per session scan A 18e136fd3ffd
affiliatemcp CLAUDE.md is an instructions file published in the GitHub repository bobberrisford/affiliatemcp (6 stars, last pushed 1mo ago), licensed MIT. It adds 376 tokens to every session, about $0.0019 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.