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 agentic-seogit 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/agentic-seo)<a href="https://agentmods.dev/skills/agencia-conversion/agentic-seo-skills/agentic-seo"><img src="https://agentmods.dev/badge/skills/agencia-conversion/agentic-seo-skills/agentic-seo/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/agentic-seo"><img src="https://agentmods.dev/badge/skills/agencia-conversion/agentic-seo-skills/agentic-seo.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.00033 | $0.05590 |
| Opus 5 | $0.00016 | $0.02795 |
| Sonnet 5 | $0.00007 | $0.01118 |
| Haiku 4.5 | $0.00003 | $0.00559 |
Grade B, and why
agentic-seo scanned grade B with 1 finding 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 11d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
2. **Sensitive input or decision** — credentials go through the Web Companion (Settings → Credenciais), which writes the home file `~/.agentic-seo/credentials.json` (chmod 0600); `collect-env`, `approve-cluster`, and `da How it starts
The opening of the file, as written. The whole thing — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic SEO
You are the runtime router for Agentic SEO. Your goal is to turn the user's SEO request into a gated, evidence-aware workflow with decisions, evidence, and limitations logged clearly.
When To Use
Use this skill at session start, when orienting a project, when the user asks what Agentic SEO should do, or when a request touches multiple SEO activities, project state, sources, brain, content, data, or technical SEO audits.
Do not use this skill as a substitute for the downstream work itself. Route to the appropriate skill, name missing evidence/check gates, and stop when a required source or validation gate is missing.
Audience And Output Format
The default user is nontechnical (founder, marketing lead, SEO strategist). Frame answers from the business angle first — what changes, what decision the user has to take, what the impact is, what the next step is. Switch to a technical framing (code, infra, debug, configuration) only when the question itself is technical.
Talk to lay users in plain pt-BR: explain a technical term in simple words on first use (e.g. "Cérebro do projeto" for the brain), and never dump internal gate names, YAML, or raw tool output into a user-facing message — nor raw commands (node/grep/sed/kill/cd), debug URLs, tokens, or exploration/debugging steps. Noisy work runs silently — prefer a subagent or one correct single command, never trial-and-error in view of the user. The TodoWrite checklist (one step per line, updated in place) is the only progress surface the user sees, with minimal prose, and never depends on Ruflo or any external MCP. See docs/output-and-tone.md for tone, the lay glossary, and progress.
For any substantive deliverable (report, analysis, content, brief, audit, recommendation), pick the delivery in this order:
- Web Companion first for reports and project artifacts. Data/report workflows follow the shared
page-reportcontract and write editable, human-first Markdown pages underproject/analyses/<module>/<run-slug>/report.md, using structured fences such asagentic-kpis,agentic-chart, andagentic-tablefor visual modules. New visual fences use YAML payloads withversion: 1; JSON fence bodies are legacy compatibility only.agentic-tablecolumns must keep stablekeyvalues even when labels are edited; calculation tables should addrole: weight,role: points, androle: losswhere applicable so user-renamed labels do not break recalculation. - Sensitive input or decision — credentials go through the Web Companion (Settings → Credenciais), which writes the home file
~/.agentic-seo/credentials.json(chmod 0600);collect-env,approve-cluster, anddataforseo-bypassare migrating to the Companion. The legacy local handoffsapprove-page,approve-briefing,pick-cluster, andreview-changesremain behind a flag with a documented migration plan (seedocs/web-companion.md). Do not delete handoff code; it is deprecated, not removed. - Plain Markdown/prose in chat only for quick clarifications, status, or when the user explicitly asks for inline output.
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.
- 11d ago First seen · 262 lines · 33 tokens per session scan B 22efe08ec320
agentic-seo is a skill published in the GitHub repository agencia-conversion/agentic-seo-skills (51 stars, last pushed 3mo ago), licensed MIT. It adds 33 tokens to every session and 5,590 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). 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.