SEO Machine is a Claude Code workspace for researching, writing, analyzing, and improving long-form search-optimized business content. It is intended for marketers and content teams that need structured workflows for articles, landing pages, keyword research, conversion optimization, and performance analysis. Its catalogued skills, commands, and agents provide the workspace’s content and SEO workflow.
Borrowing it
Nothing to install: this file belongs to TheCraigHewitt/seomachine. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TheCraigHewitt/seomachine/main/.claude/commands/performance-review.mdgit clone --depth 1 https://github.com/TheCraigHewitt/seomachineWrote 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/thecraighewitt/seomachine/performance-review)<a href="https://agentmods.dev/commands/thecraighewitt/seomachine/performance-review"><img src="https://agentmods.dev/badge/commands/thecraighewitt/seomachine/performance-review/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/thecraighewitt/seomachine/performance-review"><img src="https://agentmods.dev/badge/commands/thecraighewitt/seomachine/performance-review.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.02408 |
| Opus 5 | $0.00000 | $0.01204 |
| Sonnet 5 | $0.00000 | $0.00482 |
| Haiku 4.5 | $0.00000 | $0.00241 |
Grade A, and why
performance-review 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 11d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- performance-review — 97% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 367 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performance Review Command
Use this command to analyze content performance data and generate a prioritized queue of content tasks.
Usage
/performance-review [days]
What This Command Does
- Fetches data from Google Analytics, Google Search Console, and DataForSEO
- Analyzes performance trends and opportunities
- Identifies quick wins, declining content, and growth opportunities
- Scores and prioritizes all opportunities by ROI
- Creates actionable task queue with specific next steps
- Generates comprehensive performance report
Process
Data Collection
- Google Analytics 4: Traffic, engagement, conversions, and trends
- Google Search Console: Rankings, impressions, clicks, CTR by page and keyword
- DataForSEO: Competitive rankings, SERP features, keyword metrics
Opportunity Identification
The Performance Agent automatically identifies:
Quick Wins (Highest Priority):
- Keywords ranking positions 11-20 (page 2)
- Closest to page 1 with smallest optimization effort
- Calculated opportunity score based on impressions and position
Declining Content:
- Pages losing traffic month-over-month
- Identifies severity and potential causes
- Prioritizes by traffic volume at risk
Low CTR Opportunities:
- Pages with high impressions but low click-through rates
- Meta title/description improvements needed
- Calculates potential click gains
Trending Topics:
- Queries showing rising search volume
- Early mover advantage opportunities
- Content gaps in growing areas
Competitor Gaps:
- Keywords competitors rank for but your company doesn't
- Strategic positioning opportunities
- Estimated traffic potential
Scoring & Prioritization
Each opportunity receives a score (0-100) based on:
- Impact (50%): Potential traffic gain, conversion value, strategic importance
- Effort (30%): Time required, difficulty, resources needed
- Confidence (20%): Data quality, historical success rate, trend stability
Report Generation
Creates comprehensive report with:
- Executive summary of performance
- Priority queue (urgent/high/medium)
- Detailed opportunity analysis
- Content health dashboard
- Keyword portfolio status
- Resource allocation recommendations
- Week-by-week implementation roadmap
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.
- 11d ago First seen · 367 lines · 0 tokens per session scan A 7a71e0761e9a
performance-review is a command published in the GitHub repository TheCraigHewitt/seomachine (7,427 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,408 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.