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.
npx skills add dkadts/landing-kit-building --skill copy-analyzegit clone --depth 1 https://github.com/dkadts/landing-kit-buildingWrote 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/skills/dkadts/landing-kit-building/copy-analyze)<a href="https://agentmods.dev/skills/dkadts/landing-kit-building/copy-analyze"><img src="https://agentmods.dev/badge/skills/dkadts/landing-kit-building/copy-analyze/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/skills/dkadts/landing-kit-building/copy-analyze"><img src="https://agentmods.dev/badge/skills/dkadts/landing-kit-building/copy-analyze.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.00049 | $0.01225 |
| Opus 5 | $0.00024 | $0.00613 |
| Sonnet 5 | $0.00010 | $0.00245 |
| Haiku 4.5 | $0.00005 | $0.00122 |
Grade A, and why
copy-analyze 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 9d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/copy-analyze
Reads texts from inbox/texts/, analyzes through the lens of the client's niche, produces brief/copy-analysis.md with recommendations for design and structure.
When to use
- After
/inbox(texts validated). - BEFORE
/design-lock— copy analysis affects mood, density, section length. - Re-run if the client updates the copy.
Requirements
Required:
brief/01-business.mdfilled (especially the Niche section).brief/02-audience.mdfilled (pain points, language).- At least one text file in
inbox/texts/.
If anything is missing — refuse to work, ask to fill.
Process
Step 1. Load context Read:
brief/01-business.md— niche, competitors, convention/subversion.brief/02-audience.md— persona, pain, tone, language, triggers.brief/03-goals.md— main CTA, metrics.- All
inbox/texts/*.
Step 2. Clarify niche if needed
If the niche is described too broadly ("beauty", "services", "marketing") — re-ask until you have a sub-niche like "men's Botox for CEOs in Barcelona" or "SEO for local dentists in Germany".
Also ask if needed:
- Average check (affects copy volume and depth).
- Sales cycle (minutes vs weeks — affects section list).
- Real client phrases (voice-of-customer — gold for copy).
Step 3. Deep analysis
Walk the copy and answer each point concretely (not "generally OK").
A. What the client actually sells
- Explicit offer: literal text.
- Implicit offer: implied (people buy transformation, not the product).
- Transformation: from state A → to state B.
B. Strengths for this niche
- Unique claims — what can't be said about competitors (check 01-business.md → competitors).
- Proof — numbers / cases / credentials.
- Emotional hooks (fear / status / curiosity / belonging).
- Rational hooks (savings / efficiency / safety).
- Magic words for this niche (found in the copy, resonating with audience maturity).
C. Weaknesses
- Generic / cliché ("individual approach", "best materials", "top quality").
- Feature-talk instead of benefit-talk ("we have 5 sessions" instead of "in 5 sessions the pain goes away").
- Missed audience pains (cross with 02-audience → pain points).
- Missed objections (cross with 02-audience → objections).
- Missing social proof / guarantees / urgency where appropriate.
- Passive voice, long sentences, bureaucratese.
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.
- 9d ago First seen · 146 lines · 49 tokens per session scan A 06e9527c5f9e
copy-analyze is a skill published in the GitHub repository dkadts/landing-kit-building (2 stars, last pushed 21d ago), licensed MIT. It adds 49 tokens to every session and 1,225 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 skills, from other repositories
next-upgrade
Upgrade Next.js to the latest version following official migration guides and codemods.
deploy
Ship a build reversibly — to a host you manage or a platform that manages it. Pick the topology first, keep the previous version reachable, gate on health, roll back without rebuilding. Use when shipping anywhere users can reach.
regenerate-api
Regenerate the AppointMe frontend API client (orval/TanStack Query hooks + TypeScript schemas) after the backend OpenAPI surface changes. Use this whenever backend endpoints, request/response DTOs, or other contract-affecting types are added, removed, or modified — e.g. after editing files under src/AppointMe.Api…
db-migration
Apply schema migrations safely: detect the tool, classify the change by risk, gate destructive ones behind approval, back up in prod, preview-apply-verify, roll back on failure. Use when a schema change is about to be applied to any environment.
dependency-audit
Dependency risk assessment, read-only: known CVEs, deprecated packages, licence compliance, maintenance status, lockfile integrity, and a justification for every new dependency. Acting on it is dependency-upgrade.
verify
Build, launch, and drive the AppointMe stack to verify a change end-to-end at its runtime surface.