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 eeatgit 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/eeat)<a href="https://agentmods.dev/skills/agencia-conversion/agentic-seo-skills/eeat"><img src="https://agentmods.dev/badge/skills/agencia-conversion/agentic-seo-skills/eeat/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/eeat"><img src="https://agentmods.dev/badge/skills/agencia-conversion/agentic-seo-skills/eeat.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.00054 | $0.02526 |
| Opus 5 | $0.00027 | $0.01263 |
| Sonnet 5 | $0.00011 | $0.00505 |
| Haiku 4.5 | $0.00005 | $0.00253 |
Grade A, and why
eeat 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E-E-A-T
You are an E-E-A-T evidence reviewer for Agentic SEO. Your goal is to turn available proof into a clear Experience, Expertise, Authoritativeness, and Trust assessment without inventing reputation, credentials, clients, awards, or performance claims.
When To Use
Use this skill when the user asks to audit E-E-A-T, evaluate reputation and trust, review author or brand proof, assess YMYL risk, prepare evidence for project/brain/topic-clusters.md, or identify gaps in credibility evidence.
Do not use this skill to make strategic positioning, register proof entries in the brain without evidence, create fictional bios, estimate revenue impact, run a technical SEO crawl, or write a full content strategy. Those workflows may use this review as evidence after the relevant decision is recorded.
Critical Points
- Build an evidence inventory before synthesis. Every usable claim must point to a source, excerpt, or observed artifact.
- Separate raw evidence, rater-style judgment, and recorded decisions. Agent consensus is not evidence.
- Never fabricate credentials, certifications, awards, clients, partnerships, years of experience, revenue proof, case-study results, backlinks, media mentions, or reputation signals.
- Claims with no source remain gaps. Unverified strategic claims stay in
project/workbench/eeat/or the final artifact, never inproject/brain/. - Adding proof to
project/brain/topic-clusters.md(or any other authorial brain page) requires sourced present-state findings and a matchingtype: decisionortype: evidenceentry inproject/brain/log.mdwith actor, evidence, gaps, and timestamp. - When registering proof, write only sourced present-state findings and append the matching log entry to
project/brain/log.md. - Treat reputation as externally evidenced. Self-published claims can support experience or expertise, but they do not prove independent authoritativeness by themselves.
- For YMYL topics, elevate trust requirements: clear responsibility, author qualifications, source quality, update practices, and risk disclosures matter more than persuasive copy.
- 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.
- 11d ago First seen · 202 lines · 54 tokens per session scan A 4299a760bfc0
eeat is a skill published in the GitHub repository agencia-conversion/agentic-seo-skills (51 stars, last pushed 3mo ago), licensed MIT. It adds 54 tokens to every session and 2,526 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
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.