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/priorities)<a href="https://agentmods.dev/commands/seite-sh/seite/priorities"><img src="https://agentmods.dev/badge/commands/seite-sh/seite/priorities/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/priorities"><img src="https://agentmods.dev/badge/commands/seite-sh/seite/priorities.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.01453 |
| Opus 5.5 | $0.00000 | $0.00581 |
| Sonnet 5.5 | $0.00000 | $0.00291 |
| Haiku 4.5 | $0.00000 | $0.00145 |
Grade A, and why
priorities 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 priorities — 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Priorities Command
Generate a comprehensive, prioritized content roadmap using multiple SEO research angles.
Usage
/priorities - Comprehensive research (all modules, ~10 minutes)
/priorities quick - Quick wins only (fast, ~2 minutes)
What This Command Does
Comprehensive Mode (Default)
Runs 5 research modules to provide complete content strategy:
- Quick Wins - Keywords ranking 11-20 (page 2)
- Competitor Gaps - What competitors rank for that you don't
- Performance Matrix - Categorize all content by health
- Topic Clusters - Identify topical authority gaps
- Trending Topics - Rising search trends
Generates unified roadmap combining all insights.
Quick Mode
Runs quick wins analysis only - fast turnaround for immediate opportunities.
Process
1. Execute Quick Wins Research
Run the research_quick_wins.py script:
python research_quick_wins.py
This will:
- Pull 30 days of data from Google Search Console
- Find keywords ranking positions 11-20 (quick win opportunities)
- Cross-reference with DataForSEO for rankings and search volume
- Pull engagement metrics from Google Analytics 4
- Calculate opportunity scores based on impressions, position, commercial intent
- Generate detailed report in
research/quick-wins-YYYY-MM-DD.md
2. Read and Parse Results
- Read the generated markdown report
- Extract the top opportunities with highest opportunity scores
- Identify which URLs are already ranking (existing content to update)
- Identify keywords without ranking URLs (new content needed)
3. Categorize Opportunities
For each of the top 10 opportunities, categorize as:
EXISTING CONTENT UPDATE:
- Has a ranking URL on your site
- Content exists but needs optimization to move from page 2 to page 1
- Provide current ranking URL
- Estimate: Moderate effort, high impact
NEW CONTENT CREATION:
- No ranking URL found OR ranking position too low
- Need to create comprehensive content targeting this keyword
- Opportunity to capture search volume
- Estimate: High effort, high impact
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 · 183 lines · 0 tokens per session scan A bd89b11bdf63
priorities 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 1,453 tokens. A static security scan graded it A with 0 findings. It is 100% identical to priorities, 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.