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 page-reportgit 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/page-report)<a href="https://agentmods.dev/skills/agencia-conversion/agentic-seo-skills/page-report"><img src="https://agentmods.dev/badge/skills/agencia-conversion/agentic-seo-skills/page-report/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/page-report"><img src="https://agentmods.dev/badge/skills/agencia-conversion/agentic-seo-skills/page-report.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.00025 | $0.01236 |
| Opus 5 | $0.00013 | $0.00618 |
| Sonnet 5 | $0.00005 | $0.00247 |
| Haiku 4.5 | $0.00003 | $0.00124 |
Grade A, and why
page-report 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Page Report
Use this skill whenever an Agentic SEO workflow generates a report page for the Web Companion. It is a shared contract, not a standalone SEO module.
When To Use
Use page-report from report-producing skills and runtime code when creating or reviewing report.md for Technical SEO, Internal Links, SEO Analysis, Keyword Research, SERP Extract, Backlink Analysis, Topic Cluster, E-E-A-T, or Competitive Analysis.
Do not use this skill for public content drafts, approval handoffs, inline chat answers, raw provider captures, or authorial Brain updates that are not report pages.
Critical Points
- The canonical report path is
project/analyses/<module>/<run-slug>/report.md. - The report is the editable human presentation layer. Raw evidence, normalized YAML/JSON, logs, and operational artifacts stay in
sources/,audits/,keywords/,clusters/,eeat/, orworkbench/. - Frontmatter must include
title,slug,report_type,generated_at,status,source_artifact, andsummary; includescoreonly when the module has a real score. - Do not write
# <title>in the Markdown body. The Companion renders the title from frontmatter. - Use the project language from
project/.agentic-seo/project.json.languageunless a command has an explicit language override. Complete copy is required forpt-BRanden. - New visual fences must be YAML with
version: 1:agentic-kpis,agentic-chart, andagentic-table. JSON fences are legacy read compatibility only. - Tables must use stable lower-snake ASCII
keyvalues. User-facinglabelvalues may be translated or edited without changing keys. - Calculation tables must mark columns with
role: weight,role: points, androle: lossso score recalculation survives label edits. - Each report-producing module has
skills/<module>/contract.yamlandtemplates/analyses/<module>/report-skeleton.md; keep required H2 sections and table keys from the skeleton. - Before declaring a manual report done, run
npm run validate:reports -- --module=<module> --slug=<run-slug>or usescripts/lib/report-writer.mjs, which refuses invalid reports before writing. - Never paste raw provider JSON, object arrays,
[object Object], internal IDs, or snake_case evidence into the visual body. Convert evidence into natural language and readable tables. - Format numbers per the project language. The canonical source is
shared/locale.mjs(getProjectLanguage,formatNumber,formatPercent,canonicalKeyword). Skills either ship locale-formatted strings inagentic-table/agentic-kpiscells, or leave numbers raw for the Companion (useI18n().formatNumber/formatPercent) to format on render. Percent-bearing columns use the_pctkey suffix on the 0..100 scale. - Always return
report_mdandbrowser_prompt: { recommended: true, message: "Posso abrir o Web Companion para você ver a análise?", open_with: "project-browser" }. - Register the generated report in
project/brain/log.mdastype: decisionunless a more specific log type is required.
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 · 90 lines · 25 tokens per session scan A 4af525d07bce
page-report is a skill published in the GitHub repository agencia-conversion/agentic-seo-skills (51 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 1,236 once invoked, about $0.0001 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.