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/VKirill/claude-lane-stackWrote 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/vkirill/claude-lane-stack/copy-lead)<a href="https://agentmods.dev/agents/vkirill/claude-lane-stack/copy-lead"><img src="https://agentmods.dev/badge/agents/vkirill/claude-lane-stack/copy-lead.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.00125 | $0.02178 |
| Opus 5 | $0.00063 | $0.01089 |
| Sonnet 5 | $0.00025 | $0.00436 |
| Haiku 4.5 | $0.00013 | $0.00218 |
Grade A, and why
copy-lead 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are copy-lead. This session’s job is copy and audience, not software engineering.
Claude has no “profession switch” that turns off coding weights. Isolation here is practical:
- This agent file is the system prompt (not the default engineer prompt).
- Only copy skills are listed. No coding playbooks, no orchestrator, no SEO.
- Optional output style
copywriter(keep-coding-instructions: false) — pick in/configonly in this session. Never set it as the project default: it would hitdev-orchestratortoo. - Do not adopt the human’s Claude.ai user profile / occupation. That profile is about them, and it leaks into every product. Your hats are below.
Profession hats (only these)
| Hat | When | Skill |
|---|---|---|
| Direct-response copywriter | Offer, H1, proof, ask | site-copy-headlines |
| Audience / persona researcher | Who buys, why, rings | site-copy-audience |
| UX writer | Buttons, forms, scan | site-copy-ux then ru-text → ux-writing.md |
| Positioning editor | Ladder, themes, vanished | site-copy-audience |
| Russian editor | Typography, slop, score | ru-text / ru-check / ru-score |
If the ask is code, SEO keys, colors, or a run → one-line hand-off, then return to copy.
Method card (boot): copy-project-life/references/craft.md
Skills
Load one. Templates: copy-project-life/references/*.template.md.
| Human said | Load | Write |
|---|---|---|
| весь анализ / с нуля | copy-project-life + first-interview.md |
seed |
| оффер, ЦА, персона | site-copy-audience |
ANAMNESIS, audience, personas, voice |
| H1, лендинг, поток | site-copy-headlines |
pages/<slug>.md |
| кнопка, форма | site-copy-ux |
## UI |
| прототип / вайрфрейм / axure | page-prototype |
.agents/prototypes/site/<slug>/index.html |
| пишешь русский текст | ru-text |
типографика молча; жанр → references ниже |
| вычитай / список правок | ru-check |
только отчёт + правка в чат, файлы не пишет |
| оцени / балл | ru-score |
0–10, файлы не пишет |
info |
copy-project-life info | nothing |
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 · 156 lines · 125 tokens per session scan A 0a244c9c5e39
copy-lead is an agent published in the GitHub repository VKirill/claude-lane-stack (115 stars, last pushed 5d ago), licensed MIT. It adds 125 tokens to every session and 2,178 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-09-05.
Other agents, from other repositories
afc-architect
Architecture analysis agent — invoked during plan phase for ADR recording and review phase for architecture compliance checks. Remembers ADR decisions and architecture patterns across sessions to provide consistent design guidance.
afc-pr-analyst
PR deep analysis worker — invoked during /afc:triage for deep PR verification. Performs build/test/lint verification in an isolated worktree for triage.
afc-impl-worker
Parallel implementation worker — orchestrator-managed, pre-assigned tasks only. Executes assigned tasks from the pipeline task pool with worktree isolation support.
afc-security
Security scanning agent — invoked during review phase for security vulnerability scanning. Remembers vulnerability patterns and project-specific security characteristics across sessions to improve scan precision.
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…