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.
git clone --depth 1 https://github.com/seite-sh/seiteWrote 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/seite-sh/seite/rewrite)<a href="https://agentmods.dev/commands/seite-sh/seite/rewrite"><img src="https://agentmods.dev/badge/commands/seite-sh/seite/rewrite/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/seite-sh/seite/rewrite"><img src="https://agentmods.dev/badge/commands/seite-sh/seite/rewrite.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.02019 |
| Opus 5.5 | $0.00000 | $0.00808 |
| Sonnet 5.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 1mo 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.
This is a copy
100% identical to rewrite — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 1mo ago First seen · 260 lines · 0 tokens per session scan A 3035ad0ff600
rewrite is a command published in the GitHub repository seite-sh/seite (25 stars, last pushed 3d 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. It is 100% identical to rewrite, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
install
This page explains how the livewiki install CLI command detects installed coding agents and safely configures the livewiki MCP server entry, hook templates, shared skills, and optional pointer files.
pointer
This page documents the livewiki pointer subcommand, which manages an opt-in "pointer" block inside an AGENTS.md or CLAUDE.md file at the repository root.
index-cmd
The index command reindexes a repository and synchronizes its anchor ledger while selecting human-readable, JSON, or quiet output.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
help
Get help with the hookify plugin.