What is weekly-report?

A command for creating and rendering a weekly client report from search, website, and work-progress data. It compares the latest complete week with the previous week and produces a report deck.

Use it to report changes in search rankings, organic traffic, Google Search Console results, AI visibility, and active workstreams for a client project.

It removes the need to gather weekly performance changes and assemble the report manually.

weekly-report — Command for Claude Code by prashishh

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/prashishh/seo-geo-report-engine

agentmods

npx agentmods add commands/prashishh/seo-geo-report-engine/weekly-report

Made for: Claude Code.

Or install seo-geo-report-engine, the plugin that ships this one along with the rest of its 33 skills, 8 commands, 5 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/prashishh/seo-geo-report-engine/weekly-report/github.svg)](https://agentmods.dev/commands/prashishh/seo-geo-report-engine/weekly-report)

Your own site

<a href="https://agentmods.dev/commands/prashishh/seo-geo-report-engine/weekly-report"><img src="https://agentmods.dev/badge/commands/prashishh/seo-geo-report-engine/weekly-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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/prashishh/seo-geo-report-engine/weekly-report"><img src="https://agentmods.dev/badge/commands/prashishh/seo-geo-report-engine/weekly-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 502 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00023	$0.00502
Opus 5	$0.00012	$0.00251
Sonnet 5	$0.00005	$0.00100
Haiku 4.5	$0.00002	$0.00050

Measured 9d ago against content hash bfaf030b2df8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

weekly-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 9d 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.

commands/weekly-report.md · 39 lines

What it actually says

/weekly-report

Produce this week's client report for $1 (defaults to the active project — resolve with ./bin/mkt config show). Thin workflow: it invokes the report-generator skill for the weekly period and renders the deck. The reporting methodology and the report spec live in the skill and templates/report-weekly/.

Steps

Resolve the period. This week ending 2026-06-23 (the most recent complete week); compare against the prior week. Read client.yml for domain, ahrefs.project_id, ahrefs.brand_radar_report_id, and owned analytics ids.
Invoke report-generator (period: weekly). The skill pulls the week's deltas — rank movement (rank-tracker-overview), organic traffic/value, top movers, GSC clicks/impressions, AI SoV (brand-radar-sov-overview), and any active workstream progress — then composes a report.yml sections spec (per templates/report-weekly/). Prefer Ahrefs MCP (knowledge/ahrefs-mcp-map.md); call doc before first use; values are USD cents (÷100). Lead with what changed vs last week and why; keep it short.

Render the deck.

./bin/mkt doc build --in projects/$1/report.yml --out projects/$1/deliverables/$1-weekly-2026-06-23.pdf --project $1

Review + report back. Read the PDF: numbers consistent, charts legible, no artifacts. Summarize the week's headline movement and any flag the client should act on.

Cadence

Run weekly. For automation, schedule with /loop (/loop 1w /weekly-report $1) or the /schedule routines (a weekly cron cloud agent). Every number is falsifiable and dated; never fabricate a metric to fill a slot — show a gap instead.

Changes

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.

9d ago First seen · 39 lines · 23 tokens per session scan A bfaf030b2df8

Subscribe to this mod's changes

weekly-report is a command published in the GitHub repository prashishh/seo-geo-report-engine (5 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 502 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-31.

Analytics and metrics Documents geo marketing marketing-agents seo

seo-geo

SEO/GEO end-to-end along the SITE loop: survey demand and competitors, implement content, tune quality/tech/on-page, and evaluate authority/rankings/reports/memory (--phase survey|implement|tune|evaluate). Not sure? Use /aaron-marketing:auto.

aaron-he-zhu/aaron-marketing-skills · 58 tokens

Run a paid-ads (ROAS) workflow: audience segments, account structure, ad creative, experiment design, pre-launch signal QA + the account-audit gate, measurement, and attribution. Not sure? Use /aaron-marketing:auto.

aaron-he-zhu/aaron-marketing-skills · 50 tokens

email

Run an email-marketing (SEND) workflow: deliverability/consent setup, segmentation, email creative, lifecycle flows, newsletter monetization, send-testing, and the email-quality audit gate. Not sure? Use /aaron-marketing:auto.

aaron-he-zhu/aaron-marketing-skills · 50 tokens

influencer

Run an influencer-marketing (STAR) workflow: audience & creator scouting, campaign targeting, briefs, outreach, amplification, and ROI reporting. Not sure? Use /aaron-marketing:auto.

aaron-he-zhu/aaron-marketing-skills · 39 tokens

launch

Run a product-launch (RAMP) workflow: positioning and launch tiering, window/early-access design, message house and asset kits, the launch-readiness gate with a T-1 go/no-go, launch-day execution, and the post-launch prove loop. Not sure? Use /aaron-marketing:auto.

aaron-he-zhu/aaron-marketing-skills · 64 tokens

narrative

Run a brand-narrative & messaging (TALE) workflow: trace the current message and positioning truth, architect the durable message house/voice/story canon, land it consistently across every surface, and evaluate resonance with tests and drift monitoring. Not sure? Use /aaron-marketing:auto.

aaron-he-zhu/aaron-marketing-skills · 59 tokens