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 agencia-conversion/agentic-seo-skills --skill seo-analysisgit clone --depth 1 https://github.com/agencia-conversion/agentic-seo-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/agencia-conversion/agentic-seo-skills/seo-analysis)<a href="https://agentmods.dev/skills/agencia-conversion/agentic-seo-skills/seo-analysis"><img src="https://agentmods.dev/badge/skills/agencia-conversion/agentic-seo-skills/seo-analysis/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/agencia-conversion/agentic-seo-skills/seo-analysis"><img src="https://agentmods.dev/badge/skills/agencia-conversion/agentic-seo-skills/seo-analysis.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.00040 | $0.02265 |
| Opus 5 | $0.00020 | $0.01132 |
| Sonnet 5 | $0.00008 | $0.00453 |
| Haiku 4.5 | $0.00004 | $0.00227 |
Grade A, and why
seo-analysis 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 12d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Analysis
You are an SEO analyst for Agentic SEO. Your goal is to produce one evidence-backed SERP analysis for one keyword and market, separating raw findings from synthesis and clearly marking hypotheses.
When To Use
Use this skill when the user asks to analyze a keyword, compare ranking pages, understand SERP patterns, evaluate a target page against competitors, or interpret a player score for a keyword.
Do not use this skill to create a full content calendar, draft the article, decide strategic positioning, run backlink outreach, or write authorial brain pages. Those are separate workflows that may use this analysis as evidence after it is complete.
Critical Points
- DataForSEO is the default SERP source. Do not silently use WebSearch when DataForSEO is missing, inconvenient, or incomplete.
- WebSearch is allowed only after a bypass reason is recorded. Record actor (
agentby default), timestamp, reason, missing dimension, and consequence:not data-backed by DataForSEO. - Always record provider, provider reason, location, country or market, language, device, and generation timestamp.
- Compare the top 3 organic results when available. If fewer than 3 are available, mark the analysis incomplete and explain the limitation.
- For a target URL or domain, interpret page gaps against the ranking pages and explain the player score. Do not assume a homepage is the ranking URL.
- Mark recommendations that are not directly proven by evidence as hypotheses.
- Never fabricate keyword volume, backlinks, rankings, credentials, awards, clients, or proof. Unknown metrics stay
nullorunknown. - Keep source data separate from synthesis. Raw provider and page evidence belongs under
project/sources/; analysis drafts belong underproject/workbench/seo-analysis/. - Do not write hypotheses or unevidenced strategic conclusions to
project/brain/. - Preserve the requested output language, including pt-BR accents in generated prose:
página,conteúdo,análise,evidência,aprovação,técnico,não,até.
What ships with it
2 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.
- 12d ago First seen · 187 lines · 40 tokens per session scan A 265d77faf27b
seo-analysis is a skill published in the GitHub repository agencia-conversion/agentic-seo-skills (51 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 2,265 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-30.
Other skills, from other repositories
deep-ass-research
Deep, multi-source, primary-sourced research into a backlinked Obsidian vault. Fans out scout/diver sub-agents that write atomic cited claim notes, adversarially verifies them, then synthesizes a Map-of-Content + report. Use when the user wants thorough, cited research on a topic, company, market, or literature, or…
api-testing
HTTP API testing for TypeScript (Supertest) and Python (httpx, pytest). Test REST APIs, GraphQL, request/response validation, authentication, and error handling.
bun-test-mocking
Use for mock functions in Bun tests, spyOn, mock.module, implementations, and test doubles.
bun-test-coverage
Use for test coverage with Bun, --coverage flag, lcov reports, thresholds, and CI integration.
api-gateway-configuration
Configures API gateways for routing, authentication, rate limiting, and request transformation in microservice architectures. Use when setting up Kong, Nginx, AWS API Gateway, or Traefik for centralized API management.
api-response-optimization
Optimizes API performance through payload reduction, caching strategies, and compression techniques. Use when improving API response times, reducing bandwidth usage, or implementing efficient caching.