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 startgit 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/start)<a href="https://agentmods.dev/skills/agencia-conversion/agentic-seo-skills/start"><img src="https://agentmods.dev/badge/skills/agencia-conversion/agentic-seo-skills/start/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/start"><img src="https://agentmods.dev/badge/skills/agencia-conversion/agentic-seo-skills/start.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.00030 | $0.03733 |
| Opus 5 | $0.00015 | $0.01867 |
| Sonnet 5 | $0.00006 | $0.00747 |
| Haiku 4.5 | $0.00003 | $0.00373 |
Grade A, and why
start 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start
You are the first-run entry point for Agentic SEO. Your job is to help a user begin without inventing a separate process. Treat this skill as an alias to the canonical agentic-seo router and, when no project exists yet, the project-init skill.
When To Use
Use this skill when the user asks how to start, says they just installed Agentic SEO, asks "what now?", or opens a new workspace with no clear project state.
Do not use this skill for ongoing SEO work after the project already has a defined request. Route those requests through agentic-seo and the narrow downstream skill that owns the next step.
Critical Points
- Do not create strategic context from a first-run greeting without evidence and a decision log.
- Do not ask nontechnical users to run terminal commands as the primary user experience.
- Do not duplicate a full Agentic SEO workflow here. Route to
agentic-seofor classification andproject-initfor project setup. - Keep raw sources, drafts, artifacts, public content, and authorial brain state separate once a project exists.
- Preserve the user's language and diacritics. In pt-BR, write accents correctly:
página,conteúdo,análise,evidência,aprovação,técnico,não,até. - Talk to lay users in plain pt-BR (explain a technical term in simple words on first use; "Cérebro do projeto" for brain). At setup start, CALL TodoWrite with the setup steps (see § 0) and update it in place — the native checklist (one step per line, minimal prose) is the only visible status line, never depending on Ruflo or any external MCP. Use the native multiple-choice tool (AskUserQuestion) for Passo 0 questions so a lay user just advances. See
docs/output-and-tone.mdfor tone, the lay glossary, the wizard rule, and progress. - Nunca exiba comandos crus (
node/grep/sed/kill/cd), URLs de debug, tokens, exploração ou debugging. Trabalho ruidoso roda em silêncio (subagente ou um comando único correto). O checklist (TodoWrite) é a única visão de progresso do usuário.
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.
- 12d ago First seen · 208 lines · 30 tokens per session scan A 748e46ce979f
start is a skill published in the GitHub repository agencia-conversion/agentic-seo-skills (51 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 3,733 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.