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 agentmods add skills/jonathimer/devmarketing-skills/developer-seonpx skills add jonathimer/devmarketing-skills --skill developer-seogit clone --depth 1 https://github.com/jonathimer/devmarketing-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/skills/jonathimer/devmarketing-skills/developer-seo)<a href="https://agentmods.dev/skills/jonathimer/devmarketing-skills/developer-seo"><img src="https://agentmods.dev/badge/skills/jonathimer/devmarketing-skills/developer-seo.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 | $0.00090 | $0.01861 |
| Opus 5 | $0.00045 | $0.00931 |
| Sonnet 5 | $0.00018 | $0.00372 |
| Haiku 4.5 | $0.00009 | $0.00186 |
Grade A, and why
developer-seo 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 4d 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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer SEO
Overview
Developer SEO differs fundamentally from traditional SEO. Developers search with precise technical intent—error messages, API questions, "how to X in Y language" queries. They bounce immediately from thin content and respect sites that actually solve problems. Your competition isn't other marketing sites; it's Stack Overflow, official docs, and GitHub issues.
This skill covers SEO strategies that work for technical audiences without compromising on substance.
Understanding Developer Search Behavior
How Developers Search
Developers search differently than general audiences:
Query patterns:
- Error messages (often copy-pasted verbatim)
- "How to [action] in [language/framework]"
- "[Tool A] vs [Tool B]"
- "[Concept] tutorial"
- "[Library] [specific function] example"
Behavioral signals:
- High bounce rates on superficial content
- Long dwell time on genuinely helpful pages
- Multiple tabs open comparing solutions
- Quick scroll to code examples
- Immediate exit if content doesn't match query intent
Search Intent Categories
- Troubleshooting: Developer has an error, needs a fix
- Learning: Developer wants to understand a concept
- Evaluating: Developer comparing tools or approaches
- Implementing: Developer needs working code examples
- Reference: Developer needs quick syntax or API lookup
Keyword Research for Developers
Finding Technical Long-Tail Keywords
Technical long-tail keywords have lower volume but extremely high intent. A developer searching "axios interceptor refresh token react" knows exactly what they need.
Research approaches:
-
Mine your support channels
- Extract questions from support tickets
- Review Discord/Slack community questions
- Analyze GitHub issues for common problems
-
Stack Overflow mining
- Search for questions mentioning your tool category
- Look at related questions on popular threads
- Note the exact phrasing developers use
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 291 lines · 90 tokens per session scan A b0d0b323b167
developer-seo is a skill published in the GitHub repository jonathimer/devmarketing-skills (86 stars, last pushed 6mo ago), licensed MIT. It adds 90 tokens to every session and 1,861 once invoked, about $0.0005 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…