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 marketingskills/seo --skill client-report-writergit clone --depth 1 https://github.com/marketingskills/seoWrote 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/marketingskills/seo/client-report-writer)<a href="https://agentmods.dev/skills/marketingskills/seo/client-report-writer"><img src="https://agentmods.dev/badge/skills/marketingskills/seo/client-report-writer/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/marketingskills/seo/client-report-writer"><img src="https://agentmods.dev/badge/skills/marketingskills/seo/client-report-writer.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.00048 | $0.00669 |
| Opus 5 | $0.00024 | $0.00334 |
| Sonnet 5 | $0.00010 | $0.00134 |
| Haiku 4.5 | $0.00005 | $0.00067 |
Grade A, and why
client-report-writer 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Client Report Writer
Overview
Transforms raw GSC and GA4 data into a structured client-ready report. The report tells a clear story: what happened, why it happened, and what to do next. Works with live data or pasted exports.
Inputs
- Current period GSC data (clicks, impressions, CTR, avg position by page and query)
- Prior period GSC data for comparison
- Optional: GA4 data (sessions, users, conversions, landing pages)
- Optional: goals or KPIs the client tracks
- Optional: previous report for trend continuity
- Client name or brand voice preferences
Workflow
- Collect metrics for current and prior periods.
- Calculate period-over-period changes for all key metrics.
- Identify:
- Top-level trend (up, down, flat with magnitude).
- Pages that drove the change (top gainers, top decliners).
- Queries that drove the change.
- Technical issues detected (indexing drops, coverage changes).
- Categorize changes as:
- Expected (seasonal, planned launches, known ranking shifts).
- Actionable (fixable issues with clear ROI).
- Monitoring (needs observation before action).
- Write the report in professional narrative form.
- Add a recommendations section with prioritized actions.
Output Format
## SEO Performance Report
**Client:** [Name] | **Period:** [Range] | **Date:** [Date]
### Executive Summary
[3-5 sentence narrative of overall performance]
### Key Metrics
| Metric | Current | Prior | Change |
|---|---|---|---|
### What Changed
[Explanation of the main movements]
### Pages Driving Performance
#### Top Gainers
[Table with page, metric change, probable cause]
#### Top Decliners
[Table with page, metric change, probable cause]
### Query Trends
[Notable query movements, new opportunities, declining terms]
### Technical Health
[Index status, coverage issues, crawl stats if available]
### Recommendations
1. [Priority action with expected impact]
2. [Secondary action]
3. [Monitoring item]
### Appendix
Data sources, date ranges, methodology notes.
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 · 89 lines · 48 tokens per session scan A 6d8f26697b5d
client-report-writer is a skill published in the GitHub repository marketingskills/seo (3 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 669 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-31.
Other skills, from other repositories
os-check-work
ALWAYS invoke this skill when the user asks about work done outside this session - "check work", "check the others", "check other sessions" - or to accept one: "the session is done, check it", "can we merge it" - in any language. You are the receiving party: treat the report as a claim, verify each part against…
os-done-or-not
ALWAYS invoke this skill when work wraps up or the user asks how it went - "done or not", "are we done", "what happened", "report", "what's the status of this ticket" - in any language, and when a Stop hook asks for a session report. Produces a ten-line plain- language report: a lead, a checkmark table, and a verdict…
os-step-by-step
ALWAYS invoke this skill when you need the user to act - run a command, paste a secret, click, approve - and whenever they ask how to do something or say they do not know what to do: "step by step", "walk me through it", "what do I do", "what should I do", "I don't understand what to do", "explain what I need to do"…
os-what-could-go-wrong
ALWAYS invoke this skill before anything hard to undo gets agreed to - a contract, a purchase, a migration, a launch, a price change, a reorganisation - and whenever the user asks "what could go wrong", "what are we missing", "poke holes in this", or for a premortem or a red team, in any language. Assumes the decision…
os-whats-next
ALWAYS invoke this skill when the user asks what to do next, what is left, or what is blocked - "what's next", "what now", "what should we work on", "anything I can do" - in any language. This skill picks the next piece of work; when the user asks HOW to do a thing or says they do not understand what to do, that is…
os-big-picture
ALWAYS invoke this skill when the user asks where the project as a whole stands - "where are we", "what's the big picture", "what have we built", "what is in this project", "map the project", "what does this thing even do", "what is stale", "what can we delete", "update the roadmap" - in any language, and whenever a…