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/mblode/agent-skills/seo-programnpx skills add mblode/agent-skills --skill seo-programgit clone --depth 1 https://github.com/mblode/agent-skillsWhat 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.00204 | $0.02171 |
| Opus 5 | $0.00102 | $0.01086 |
| Sonnet 5 | $0.00041 | $0.00434 |
| Haiku 4.5 | $0.00020 | $0.00217 |
Grade A, and why
seo-program 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 3d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Program
- IS: demand research with live numbers, answer-engine question maps, writer content briefs, and the monitoring cadence that reports whether any of it worked.
- IS NOT: choosing which topics to cover or building content pillars and an editorial calendar (
content-strategy), AI-search content tactics and citation strategy (ai-seo), implementing the page in code (optimise-seoowns metadata, schema, canonicals,llms.txt), writing the article (externalghostwriterwith the blog profile), or short-form product copy (copywriting). This skill starts once a topic is chosen and ends when the brief is handed over.
Mode dispatch
| The ask | Mode |
|---|---|
| Volumes, a question map, or a brief for one topic | Topic pipeline |
| Search Console review, a traffic drop, recurring checks | Monitoring |
Either mode needs the tool binding below on first run.
Setup: bind jobs to tools
Read what is actually connected before asking anything. Then propose one tool per job and ask only about the jobs with no connected option.
| Job | Typical tools |
|---|---|
| Keyword volume | Semrush, Ahrefs, Google Ads Keyword Planner in a signed-in browser |
| Prompt and AI visibility | Profound, or the connected AI-visibility tool |
| Search performance | Google Search Console via connector or signed-in browser |
| Docs and pipeline | Notion, Google Sheets or Docs, Linear, Airtable |
| Team chat and recaps | Slack, Teams, email |
| Call recordings (demand signals) | whatever recording tool is connected |
No vendor is required. Name a tool when it is connected, fall back to the next connected option when it is not, and say plainly when a job has nothing behind it rather than working around the gap silently. Never state that a tool is connected without having seen it.
If a tool needs a login, hand the browser over and let the user sign in. Never type credentials.
Mode A: Topic pipeline
Copy and track this checklist:
Topic pipeline progress:
- [ ] Step 1: Pull live keyword and prompt volumes for the topic
- [ ] Step 2: Build the question map
- [ ] Step 3: Write the brief
- [ ] Step 4: Hand over the numbers table as evidence
What ships with it
3 files 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.
- 3d ago First seen · 123 lines · 204 tokens per session scan A e992fcfad080
seo-program is a skill published in the GitHub repository mblode/agent-skills (95 stars, last pushed 3d ago), licensed MIT. It adds 204 tokens to every session and 2,171 once invoked, about $0.0010 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…