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/research-performance)<a href="https://agentmods.dev/commands/seite-sh/seite/research-performance"><img src="https://agentmods.dev/badge/commands/seite-sh/seite/research-performance/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/research-performance"><img src="https://agentmods.dev/badge/commands/seite-sh/seite/research-performance.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.00469 |
| Opus 5.5 | $0.00000 | $0.00188 |
| Sonnet 5.5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
research-performance 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 research-performance — 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Performance Command
Categorize all content by traffic and rankings to prioritize optimization.
Usage
/research-performance
What This Command Does
Analyzes ALL your blog content and categorizes into 4 performance quadrants:
- ⭐ Stars - High traffic + Good rankings → Maintain & expand
- 🚀 Overperformers - High traffic + Poor rankings → Learn why, improve SEO
- ⚠️ Underperformers - Low traffic + Good rankings → Fix CTR (title/meta)
- 📉 Declining - Low traffic + Poor rankings → Refresh or redirect
For each piece:
- Traffic trends (rising/stable/declining)
- Expected vs actual traffic
- Specific action recommendations
- Priority level
Process
Execute the performance matrix analysis:
python3 research_performance_matrix.py
This will:
- Fetch all pages from GA4 (last 90 days)
- Filter to content pages only
- Enrich with GSC ranking data
- Calculate traffic trends (180-day comparison)
- Categorize into performance quadrants
- Generate report:
research/performance-matrix-YYYY-MM-DD.md
Output
The report includes:
- Distribution across 4 quadrants
- Top performers in each category
- Specific action steps per article
- Expected traffic calculations
- Priority recommendations
Key Insights
Stars: Your best content - keep fresh, expand with clusters Underperformers: QUICK WINS - rewrite titles/meta for better CTR Declining: Content losing traction - needs refresh or redirect Overperformers: Getting traffic despite poor rankings - improve SEO
Integration
After running /research-performance:
- Use
/analyze-existing [URL]for detailed content analysis - Fix underperformer titles/meta first (low effort, high impact)
- Refresh declining stars to prevent traffic loss
Time & Requirements
Time: 2-4 minutes Requirements: GA4 required, GSC recommended Cost: Free
When to Run
- Monthly: Monitor content health
- After major updates: Track impact
- When traffic drops: Identify declining content
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 · 72 lines · 0 tokens per session scan A 49cdb9cc8faf
research-performance 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 469 tokens. A static security scan graded it A with 0 findings. It is 100% identical to research-performance, 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.