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/rewrite.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/rewrite)<a href="https://agentmods.dev/commands/thecraighewitt/seomachine/rewrite"><img src="https://agentmods.dev/badge/commands/thecraighewitt/seomachine/rewrite.svg" alt="Measured on agentmods" 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.02019 |
| Opus 5 | $0.00000 | $0.01009 |
| Sonnet 5 | $0.00000 | $0.00404 |
| Haiku 4.5 | $0.00000 | $0.00202 |
Grade A, and why
rewrite 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 8d 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:
- rewrite — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rewrite Command
Use this command to update and improve existing blog posts based on analysis findings.
Usage
/rewrite [topic or analysis file]
What This Command Does
- Takes existing blog post content and improvement recommendations
- Rewrites content with updated information and SEO optimization
- Maintains original article structure where effective
- Adds new sections to fill content gaps
- Updates outdated statistics, examples, and references
Process
Pre-Rewrite Review
- Original Content: Read the existing article thoroughly
- Analysis Report: Review findings from
/analyze-existingif available - Research Brief: Check if new research brief exists for updated angles
- Brand Voice: Verify alignment with current @context/brand-voice.md
- SEO Guidelines: Apply latest requirements from @context/seo-guidelines.md
- Competitive Context: Understand what's changed in SERP since original publication
Rewrite Strategy
Determine Scope
Based on analysis, classify the rewrite level:
- Light Update (20-30% changes): Fix stats, add keywords, improve meta
- Moderate Refresh (40-60% changes): Restructure sections, expand content, update examples
- Major Rewrite (70-90% changes): New outline, significant expansion, fresh angle
- Complete Overhaul (90%+ changes): Essentially new article on same topic
What to Keep
- Sections that are still accurate and comprehensive
- Unique insights or perspectives that remain valuable
- Well-performing structure or formatting
- Examples or case studies that are still relevant
- Internal links that remain appropriate
What to Update
- Outdated statistics with current data (note date/source)
- Old screenshots or examples with current versions
- Deprecated terminology or processes
- Missing keywords in headings and body
- Weak or missing meta title/description
- Insufficient internal links
What to Add
- New sections to fill competitive content gaps
- Recent industry trends or developments
- Additional examples or use cases
- Better introduction hook if current one is weak
- Stronger conclusion and CTA
- Missing SEO elements (keywords, links, structure)
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.
- 8d ago First seen · 260 lines · 0 tokens per session scan A 3035ad0ff600
rewrite is a command published in the GitHub repository TheCraigHewitt/seomachine (7,407 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,019 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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.