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.
git clone --depth 1 https://github.com/Affitor/affiliate-skillsWrote 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/commands/affitor/affiliate-skills/review)<a href="https://agentmods.dev/commands/affitor/affiliate-skills/review"><img src="https://agentmods.dev/badge/commands/affitor/affiliate-skills/review.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.00000 | $0.00250 |
| Opus 5 | $0.00000 | $0.00125 |
| Sonnet 5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
review 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 8d 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
Review a skill for quality before merge.
Read the skill's SKILL.md and all reference files, then check against this list:
Checklist
- Frontmatter:
nameanddescriptionpresent - Description covers 5+ trigger phrases
- Input Schema defined with required/optional fields and defaults
- Workflow section: clear step-by-step instructions
- Output Schema defined with typed fields
- Output Format: human-readable format specified
- Error Handling: covers data unavailable, missing input, fallbacks
- 2+ examples with realistic prompts
- References in separate files (if >50 lines)
- FTC affiliate disclosure mentioned
- Affitor branding in page outputs (if applicable)
- Works standalone (test: can a stranger use this with zero context?)
- Works in chain (test: does output feed cleanly into next stage?)
- Output is portable (can be used outside Claude immediately)
Report format
For each item: PASS / FAIL / N/A with a one-line note. End with: overall verdict (Ready to merge / Needs changes) and specific action items.
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.
- 8d ago First seen · 26 lines · 0 tokens per session scan A 66cfca31b8ce
review is a command published in the GitHub repository Affitor/affiliate-skills (651 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 250 tokens. 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 commands, from other repositories
review
Review code changes against project conventions.
gh-triage
GitHub OSS maintainer lifecycle triage, review, and approval management.
review
Review the current diff against project memory.
code-review
Code review a pull request.
tldr-review
One-line TLDR PR review comments (verdict first, no filler).
lfe-complexity-check
Inspector sub-skill. Analyses changed code for cyclomatic complexity, excessive nesting, oversized functions, and cognitive load indicators. Pure LLM reasoning — no external tooling. Writes .plans/checks/complexityfindings.md. Called by lfe-inspector when enabled in inspector-config.md.