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.
npx agentmods add commands/seite-sh/seite/optimizegit clone --depth 1 https://github.com/seite-sh/seiteWhat 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 | $0.00000 | $0.02402 |
| Opus 5 | $0.00000 | $0.01201 |
| Sonnet 5 | $0.00000 | $0.00480 |
| Haiku 4.5 | $0.00000 | $0.00240 |
Grade A, and why
optimize 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 2d 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
92% identical to optimize — 14 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Optimize Command
Use this command to perform a final SEO optimization pass on completed articles before publishing.
Usage
/optimize [article file]
What This Command Does
- Performs comprehensive SEO audit of article
- Fine-tunes keyword placement and density
- Optimizes meta elements for SERP performance
- Validates internal and external links
- Ensures all SEO best practices are met
Process
Content Audit
Keyword Analysis
- Primary Keyword Density: Check 1-2% density throughout article
- Keyword Placement Check:
- In H1 headline
- In first 100 words
- In at least 2-3 H2 headings
- In meta title
- In meta description
- In URL slug
- Semantic Variations: Verify related keywords are used naturally
- Keyword Stuffing: Ensure no over-optimization or unnatural usage
- LSI Keywords: Confirm latent semantic keywords are present
Heading Structure
- H1: Only one H1, includes primary keyword
- H2s: 4-7 H2 sections, at least 2-3 with keyword variations
- H3s: Proper nesting under H2s, descriptive and keyword-rich
- Hierarchy: Logical progression, no skipped levels (H1→H3)
- Length: Headings are descriptive but concise
Content Quality
- Word Count: Minimum 2000 words (2500-3000+ preferred)
- Paragraph Length: Average 2-4 sentences, no walls of text
- Sentence Length: Varied, averaging under 25 words
- Readability Score: 8th-10th grade level (Flesch-Kincaid)
- Active Voice: Predominantly active voice usage
- Transition Words: Smooth flow between sections
- List Usage: Bullets/numbers for scannability
- Formatting: Bold, italics used appropriately for emphasis
Link Optimization
Internal Links (3-5+ required)
- Quantity: Count current internal links to seite content
- Quality: Verify links are contextually relevant
- Anchor Text: Check for keyword-rich, descriptive anchor text
- Placement: Natural integration within body content
- Variety: Links to different page types (pillar, blog, product, resources)
- Reference: Cross-check @context/internal-links-map.md for opportunities
- Broken Links: Verify all internal links work
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.
- 2d ago First seen · 269 lines · 0 tokens per session scan A 0bdd8b6fcf6a
optimize is a command published in the GitHub repository seite-sh/seite (19 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,402 tokens. A static security scan graded it A with 0 findings. It is 92% identical to optimize, differing in 14 lines, and is treated as a copy.
Other commands, from other repositories
fieldtheory
Explain and drive the Field Theory CLI — bookmark-sourced seeds, repo-aware possibility runs that score ideas onto a 2x2 grid, and the interconnected .md files they leave behind. Trigger when the user asks about ft, bookmarks, seeds, ft possible (or the older name ft ideas), grids, dots/nodes, or how to turn saved…
wiki-query
Ask questions against the wiki. Synthesizes answers from wiki pages with cross-reference citations.
wiki-digest
Generate a daily or weekly digest of wiki changes — new sources, pages, insights, and gaps.
prd-triage
Triage pending findings on the active PRD.
issue-amend
Re-snapshot the active issue's scope from the spec, clear verified and reviewed receipts, and record the change as a permanent amendment.
q-research
Read the research-mode skill's SKILL.md for the full ruleset before proceeding. Follow all constraints, the source lookup cascade, the token budget, and the "what counts as cited" rules exactly.