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.
git clone --depth 1 https://github.com/jadedagher/seo-agent-stackWrote 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/commands/jadedagher/seo-agent-stack/report-seo)<a href="https://agentmods.dev/commands/jadedagher/seo-agent-stack/report-seo"><img src="https://agentmods.dev/badge/commands/jadedagher/seo-agent-stack/report-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/commands/jadedagher/seo-agent-stack/report-seo"><img src="https://agentmods.dev/badge/commands/jadedagher/seo-agent-stack/report-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.00000 | $0.00189 |
| Opus 5.5 | $0.00000 | $0.00076 |
| Sonnet 5.5 | $0.00000 | $0.00038 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
report-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 2mo 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.
What it actually says
Generate a quarterly SEO performance report for the client.
The report is a standalone HTML file in rapport/, visually polished, ready to be converted to PDF.
Instructions
- Read the skill
report-seoin.claude/skills/report-seo.mdfor the exact report structure - Read
CLAUDE.mdfor GA4 Property ID and GSC Property - Collect GA4 and GSC data for the last 12 months (see detailed queries in the skill)
- Generate the HTML file in
rapport/rapport-seo-[MONTH]-[YEAR].html - Open the report in the browser for verification
Reminders
- The client is NOT technical: simple language, no jargon
- Define each term (visitor, page view, impression, click)
- Highlight growth and positive trends
- Use the color palette defined in the skill (match the site's branding)
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.
- 2mo ago First seen · 19 lines · 0 tokens per session scan A d74e50b2af94
report-seo is a command published in the GitHub repository jadedagher/seo-agent-stack (22 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 189 tokens. 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.
report-seo compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| report-seojadedagher/seo-agent-stack | Command | 22 | 7mo ago | MIT | A | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |