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 gtmagents/gtm-agents --skill seo-writinggit clone --depth 1 https://github.com/gtmagents/gtm-agentsWrote 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/gtmagents/gtm-agents/seo-writing)<a href="https://agentmods.dev/skills/gtmagents/gtm-agents/seo-writing"><img src="https://agentmods.dev/badge/skills/gtmagents/gtm-agents/seo-writing/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/gtmagents/gtm-agents/seo-writing"><img src="https://agentmods.dev/badge/skills/gtmagents/gtm-agents/seo-writing.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.00021 | $0.00365 |
| Opus 5 | $0.00010 | $0.00182 |
| Sonnet 5 | $0.00004 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
seo-writing 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.
What it actually says
SEO Writing Skill
When to Use
- Need pillar/blog content that ranks for a target keyword cluster.
- Building briefs for writers or agencies.
- Auditing existing posts for optimization opportunities.
Framework
- Intent Mapping – classify keyword as informational, navigational, transactional; align CTA accordingly.
- SERP Analysis – review top 10 results, note content format, length, missing gaps.
- Outline Structure – mirror winning patterns while adding unique POV/data.
- On-Page Elements – optimize title tag (<60 chars), meta description, H1/H2, schema, image alt text.
- Internal/External Links – add minimum 3 internal + 3 authoritative external links.
- Conversion Hooks – insert CTA blocks, lead magnets, or inline product mentions every ~500 words.
Templates
- Keyword brief template with intent, primary/secondary keywords, CTA, internal targets.
- SERP gap analysis worksheet capturing competitor format, word count, differentiators.
- SEO QA workflow checklist (draft → optimization → publish → refresh schedule).
Tips
- Refresh top posts quarterly—update stats, add new internal links, re-fetch schema.
- Use heatmaps/scroll data to validate placement of conversion hooks.
- Coordinate with demand gen to align CTAs with current offers.
- Keep keyword cannibalization tracker so multiple teams don’t target same phrase.
Checklist
- Include primary keyword in H1 + first 100 words.
- Use semantic variants (LSI terms) per section.
- Ensure readability score < grade 9.
- Add FAQ or snippet-ready section.
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 · 39 lines · 21 tokens per session scan A ce642873aea3
seo-writing is a skill published in the GitHub repository gtmagents/gtm-agents (399 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 365 once invoked, about $0.0001 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-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…