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 tahirraufkeeyu/software-development-agent-stack--sdas --skill seo-optimizergit clone --depth 1 https://github.com/tahirraufkeeyu/software-development-agent-stack--sdasWrote 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/tahirraufkeeyu/software-development-agent-stack--sdas/seo-optimizer)<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/seo-optimizer"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/seo-optimizer.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.00063 | $0.02477 |
| Opus 5 | $0.00032 | $0.01239 |
| Sonnet 5 | $0.00013 | $0.00495 |
| Haiku 4.5 | $0.00006 | $0.00248 |
Grade A, and why
seo-optimizer 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 8d 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
Trigger this skill when the request includes any of:
- "SEO review this draft before it goes live"
- "Do keyword research for [topic]"
- "Optimize this landing page"
- "What should the meta tags be for the new case study?"
- A finished draft plus a request to "make sure this ranks"
Do not use for paid search copy (different playbook), technical SEO audits of a whole domain (that is a separate engagement), or link-building outreach.
Inputs
Required:
- Page URL or draft content — the thing being optimized.
- Primary goal — one of: rank for a specific query, capture organic traffic for a topic cluster, or improve CTR on an existing page.
Optional:
- Seed keyword — if known. If not, the skill will derive one from the content.
- Target audience intent — helps disambiguate between a "how to" and "best X tools" angle.
- Competitor URLs already ranking for the query.
Outputs
A single SEO brief containing:
- Keyword map — seed keyword, 8-15 related queries grouped by intent (informational, navigational, commercial, transactional).
- On-page recommendations:
- Title tag (≤60 chars).
- Meta description (≤155 chars).
- H1 (exactly one, matches intent).
- H2/H3 outline with keywords in natural placement.
- Internal links (minimum 3, to relevant cluster pages).
- External links (minimum 1 to a high-authority source).
- Image alt text suggestions for every image.
- Schema.org markup — the JSON-LD block to embed (
Article,FAQPage,HowTo,Product, orBreadcrumbListas appropriate). - Core Web Vitals checklist — what to verify before publish.
- Gap note — 2-3 bullets on what the current draft is missing vs the top-ranking competitors.
Tool dependencies
- WebSearch / web-fetch (required) — for SERP checks, competitor pulls, and Google auto-suggest.
- Optional: Google Search Console MCP (if available) for existing-page CTR data.
Procedure
1. Keyword research
- Start with the seed. If not provided, extract it from the page's thesis. The seed should be 2-4 words.
- Pull related queries. Use WebSearch for:
- Google auto-suggest (
seed + a-z) for long-tail variants. - "People also ask" box for the seed.
- Top 10 SERP results — scan their H1s and H2s for recurring phrases.
- Google auto-suggest (
- Classify intent for each query:
- Informational: "what is X," "how does X work," "X explained" — user wants to learn.
- Navigational: "X brand name," "X login," "X docs" — user wants a specific site.
- Commercial: "best X," "X vs Y," "X alternatives," "X reviews" — user is comparing.
- Transactional: "buy X," "X pricing," "X free trial," "X demo" — user is ready to act.
- Filter to relevance. Drop queries that do not match the page's goal. A case study should not try to rank for transactional queries.
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.
- 8d ago First seen · 248 lines · 63 tokens per session scan A cfaf1d76138b
seo-optimizer is a skill published in the GitHub repository tahirraufkeeyu/software-development-agent-stack--sdas (18 stars, last pushed 4mo ago), licensed MIT. It adds 63 tokens to every session and 2,477 once invoked, about $0.0003 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.
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…