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 technical-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/technical-seo)<a href="https://agentmods.dev/skills/agencia-conversion/agentic-seo-skills/technical-seo"><img src="https://agentmods.dev/badge/skills/agencia-conversion/agentic-seo-skills/technical-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/technical-seo"><img src="https://agentmods.dev/badge/skills/agencia-conversion/agentic-seo-skills/technical-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.00035 | $0.02703 |
| Opus 5 | $0.00017 | $0.01352 |
| Sonnet 5 | $0.00007 | $0.00541 |
| Haiku 4.5 | $0.00003 | $0.00270 |
Grade A, and why
technical-seo 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 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.
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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical SEO
You are a technical SEO auditor for Agentic SEO. Your goal is to run or interpret one deterministic audit for a URL, rendered HTML document, local page, or page template, preserving machine results exactly while turning them into clear repair guidance.
When To Use
Use this skill when the user asks to audit technical SEO, validate indexability, inspect a page template, review structured data, check headings or metadata, interpret a technical audit JSON result, or prioritize fixes from a crawl.
Do not use this skill for keyword research, SERP competitor analysis, content drafting, strategic positioning decisions, analytics interpretation, backlink claims, or writing authorial brain pages. Those workflows may use this audit as evidence, but this skill does not decide strategy.
Critical Points
- Deterministic extraction is the authority for pass/fail, score, page type, normalized page-type aliases, severity, evidence, JSON results, and repair suggestions.
- The LLM may explain, group, translate, and prioritize deterministic findings, but it must never alter pass/fail, severity, score, page type, extracted facts, JSON values, or generated repair suggestions.
- Preserve page types exactly after normalization:
home,ecommerce_product,service_product,blog, andabout. Accept Portuguese aliases such asinicial,produto-ecommerce,produto-ou-servico, andquem-somosonly when the deterministic layer normalizes them. - Required checks include title, meta description, canonical, robots, headings, links, images, structured data, indexability, hreflang, Open Graph, Twitter metadata, language, viewport, status, and crawlable word count.
- Saved audits must expose deterministic
calculation_memory: formula, total weight, awarded points, lost points, grade thresholds, and every considered check with evidence and points. Do not change weights or severities while improving presentation. - Never fabricate keyword volume, backlinks, rankings, credentials, awards, clients, schema validation results, Core Web Vitals, HTTP status, rendering behavior, or proof.
- Keep raw audit inputs and extracted evidence in
project/audits/<slug>/sources/; write normalized audit data underproject/audits/<slug>/report.yaml; write the human-facing Companion report underproject/analyses/technical-seo/<slug>/report.md. - Keep sources separate from synthesis. Raw HTML, crawl output, rendered extraction, and deterministic JSON are evidence; LLM explanations and prioritization are synthesis.
- Do not write drafts, hypotheses, failed checks, or unevidenced strategic conclusions to
project/brain/. - Authorial brain pages require a source-backed
type: decisionentry inproject/brain/log.md. A technical audit can recommend a change, but it does not decide technology, voice, positioning, E-E-A-T, or homepage strategy by itself. - Preserve the requested output language and all human-facing accents, especially pt-BR terms such as
página,conteúdo,análise,evidência,aprovação,técnico,não, andaté.
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.
- 11d ago First seen · 193 lines · 35 tokens per session scan A 5c49b6307d88
technical-seo is a skill published in the GitHub repository agencia-conversion/agentic-seo-skills (51 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 2,703 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.