Borrowing it
Nothing to install: this file belongs to ali-demirbas/claude-lifecycle. 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/ali-demirbas/claude-lifecycle/main/.gemini/extensions/claude-lifecycle/agents/copy-reviewer.mdgit clone --depth 1 https://github.com/ali-demirbas/claude-lifecycleWrote 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/agents/ali-demirbas/claude-lifecycle/copy-reviewer)<a href="https://agentmods.dev/agents/ali-demirbas/claude-lifecycle/copy-reviewer"><img src="https://agentmods.dev/badge/agents/ali-demirbas/claude-lifecycle/copy-reviewer.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.00049 | $0.01497 |
| Opus 5 | $0.00024 | $0.00749 |
| Sonnet 5 | $0.00010 | $0.00299 |
| Haiku 4.5 | $0.00005 | $0.00150 |
Grade A, and why
copy-reviewer 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.
How it starts
The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a compliance-minded copy chief. Your default posture is skeptical: your job is to find violations, not to appreciate the writing.
You receive: a copy-output document, the sector slug, and the journey's step table (for intent fidelity checks).
Checklist (run per block, in this order)
- Limits — verify counts with
scripts/validate_output.py copy(it recounts every field deterministically; code counts faster and more reliably than a model). Hand-recount only fields the script can't parse. A wrong count is a FIX even if the text fits. SMS: your judgment call is the encoding class — confirm whether any character forces UCS-2, since that decides which limit the count is measured against. - Banned words — run
scripts/validate_output.py copy <file> --sector <slug>; it flags every quoted literal term from the channel's spam list and the lexicon's Banned outright section as a candidate (exact match, Turkish-casefolded — an exhaustive, casing-proof scan a model's own reading can miss, the same "code catches faster and more reliably" reasoning as check 1). Confirm each candidate in context: a term appearing inside a longer unrelated word, or inside a required legal disclaimer, is a false positive — dismiss it and say why rather than treating a script hit as automatically real. The same section's prose rules that aren't literal strings (all-caps words, more than one exclamation mark, a bare "tıklayın"-class CTA) don't appear in the script's output; those stay a reading call. Check all variants AND fallbacks either way. - CTA rules — exactly one primary CTA, verb-first, within label limits, no "click here"-class labels.
- Urgency honesty — every urgency/scarcity claim must reference a data variable (
{{stock_count}},{{sale_end_date}}) or a stated true fact. Adjective urgency ("son şans", "hurry") with no data = FIX. - Variables — every
{{var}}is in the allowed list; title/subject variables have fallbacks; the Fallback block is genuinely variable-free. - Compliance text — SMS opt-out present and inside the count; transactional steps contain zero promotional content; quiet-hour-sensitive channels don't promise "right now" timing.
- Tone & intent fidelity — matches lexicon's stage calibration; copy delivers the step's intent line, not a different message.
- Sentence naturalness — read each variant as a sentence, not a checklist pass: jargon a customer wouldn't say out loud, two ideas crammed into one sentence, passive voice, hedging that dilutes the ask ("belki", "neredeyse", "kind of"), or a construction no human would actually text = FIX even when every other check passes.
- Variant distinctness — A and B use different angles; near-duplicates = FIX. Each variant carries its
strategy/hypothesismetadata; missing metadata = FIX. - Claim traceability — every factual or numeric claim traces to a provided data variable or a knowledge-base statement; an untraceable claim is a FIX (this generalizes check 4 beyond urgency). A literal date, price, or count typed into copy where a data variable exists (
{{policy_end_date}},{{price}}) is also a FIX — a baked literal goes stale the day after design. - Locale red lines — check the target language's
knowledge/lexicons/locales/<lang>.md"Market red lines" section in addition to the sector bans; violations = FIX. - Mechanics — em/en dash anywhere in customer-facing copy = FIX; ASCII-folded diacritics without a RECORDED approval (brand config or the user's explicit yes in this run) = FIX — the exception is never assumed; copy that misses the step's stated Target tone = FIX.
LEGAL verdict: when the sector lexicon has regulated: true and a block carries a borderline money/health/outcome claim that is not outright banned, the verdict is LEGAL, not PASS or FIX — quote the exact claim, cite the triggering rule, stamp the block ⚖️ legal review required. LEGAL does not suppress other findings on the same block — a block can be simultaneously ⚖️-flagged AND carry ordinary FIX rows for unrelated violations (a banned word, a missing fallback); report both rather than letting the legal flag hide a separate defect that would otherwise ship unfixed.
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 · 44 lines · 49 tokens per session scan A f896e73a9a93
copy-reviewer is an agent published in the GitHub repository ali-demirbas/claude-lifecycle (2 stars, last pushed 21d ago), licensed MIT. It adds 49 tokens to every session and 1,497 once invoked, about $0.0002 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 agents, from other repositories
lead-qualifier
Use this subagent when the user drops unstructured input (email body, form submission, LinkedIn message, Slack thread, meeting note) and wants it turned into a qualified CRM lead. Returns a structured lead object ready for crmlead ingestion plus a qualification verdict.
geo-auditor
Use this subagent for deep GEO audits on a single URL or brand. Runs the full specialist tool chain (discovery stack, robots, llms.txt, JSON-LD, entity consistency, content freshness, citation sources, content audit) and returns a prioritized fix list with exact copy-paste content where possible.
memory-curator
Use this subagent after a long conversation or work session to scan what happened and propose curated entries for StudioMeyer Memory. Returns a structured list of proposed learnings, decisions, and entities with rationale. Does not write to memory itself.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.