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.
git clone --depth 1 https://github.com/seite-sh/seitenpx agentmods add commands/seite-sh/seite/performance-reviewWrote 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/performance-review)<a href="https://agentmods.dev/commands/seite-sh/seite/performance-review"><img src="https://agentmods.dev/badge/commands/seite-sh/seite/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/seite-sh/seite/performance-review"><img src="https://agentmods.dev/badge/commands/seite-sh/seite/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.5 | $0.00000 | $0.00963 |
| Sonnet 5.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 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
97% identical to performance-review — 4 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 — 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 seite 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.
- 1mo ago First seen · 367 lines · 0 tokens per session scan A 654df3efab48
performance-review 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,408 tokens. A static security scan graded it A with 0 findings. It is 97% identical to performance-review, differing in 4 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.