What is monthly-report?

A command that creates a monthly client report as a presentation. It compares the latest complete calendar month with earlier performance and includes progress, results, work completed, and next priorities.

Use it to produce recurring client presentations covering traffic, search visibility, goals, wins, misses, content, links, and the next month’s plan.

It removes the need to gather monthly SEO data and assemble the same client update by hand.

monthly-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/monthly-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/monthly-report/github.svg)](https://agentmods.dev/commands/prashishh/seo-geo-report-engine/monthly-report)

Your own site

<a href="https://agentmods.dev/commands/prashishh/seo-geo-report-engine/monthly-report"><img src="https://agentmods.dev/badge/commands/prashishh/seo-geo-report-engine/monthly-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/monthly-report"><img src="https://agentmods.dev/badge/commands/prashishh/seo-geo-report-engine/monthly-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 535 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.00535
Opus 5	$0.00012	$0.00267
Sonnet 5	$0.00005	$0.00107
Haiku 4.5	$0.00002	$0.00053

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

Security

Grade A, and why

monthly-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 10d 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/monthly-report.md · 39 lines

What it actually says

/monthly-report

Produce the monthly 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 monthly period and renders the deck. The reporting methodology and the report spec live in the skill and templates/report-monthly/.

Steps

Resolve the period. The last complete calendar month — May 2026 (2026-05-01 → 2026-05-31), as of today 2026-06-23 — compared against the prior month and, where useful, the same month last year (YoY). Read client.yml for domain, ahrefs.project_id, ahrefs.brand_radar_report_id, and owned analytics ids.
Invoke report-generator (period: monthly). The monthly view is more strategic than the weekly: trend lines (*-metrics-history, gsc-performance-history, brand-radar-sov-history), goal pacing against the proposal's KPI targets, top wins and misses, content/links shipped, and the next month's focus. Composes a report.yml sections spec (per templates/report-monthly/). Prefer Ahrefs MCP (knowledge/ahrefs-mcp-map.md); call doc before first use; USD cents (÷100).

Render the deck.

./bin/mkt doc build --in projects/$1/report.yml --out projects/$1/deliverables/$1-monthly-2026-05.pdf --project $1

Review + report back. Read the PDF: numbers consistent across sections, trend charts legible, page breaks clean. Summarize the month vs target, the wins/misses, and the next focus.

Cadence

Run monthly. For automation, schedule with /loop (/loop 1mo /monthly-report $1) or the /schedule routines (a monthly cron cloud agent). Tie progress to the proposal's KPI targets so the client sees pacing. Every number is dated and falsifiable; never fabricate to fill a slot.

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.

10d ago First seen · 39 lines · 23 tokens per session scan A cd671caba1a8

Subscribe to this mod's changes

monthly-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 535 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

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

social

Run an organic-social (ECHO) workflow: channel portfolio and voice dossiers, platform-native content and calendars, the social-quality gate with a pre-publish go/no-go, community/inbox/crisis operations, and the listening/SOV/dark-social measurement loop. Not sure? Use /aaron-marketing:auto.

aaron-he-zhu/aaron-marketing-skills · 64 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.