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/analyze-existinggit 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/analyze-existing)<a href="https://agentmods.dev/commands/seite-sh/seite/analyze-existing"><img src="https://agentmods.dev/badge/commands/seite-sh/seite/analyze-existing.svg" alt="Measured on agentmods" 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.01309 |
| Opus 5 | $0.00000 | $0.00655 |
| Sonnet 5 | $0.00000 | $0.00262 |
| Haiku 4.5 | $0.00000 | $0.00131 |
Grade A, and why
analyze-existing 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 5d 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
98% identical to analyze-existing — 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Existing Command
Use this command to review and analyze existing seite blog posts for SEO opportunities, content gaps, and improvement areas.
Usage
/analyze-existing [URL or file path]
What This Command Does
- Fetches and analyzes existing blog post content
- Evaluates current SEO performance and optimization
- Identifies outdated information or statistics
- Suggests content expansion opportunities
- Provides actionable improvement recommendations
Process
Content Analysis
- URL/File Input: Accept either a live URL or local file path
- Content Extraction: Pull the full article text, headings, and structure
- Publication Date Check: Note when content was originally published
- Current Relevance: Identify outdated information, statistics, or references
- Completeness: Assess if topic coverage is comprehensive or has gaps
SEO Audit (Enhanced with New Analysis Tools)
- Search Intent Analysis (NEW!): Determine if content matches user search intent (informational/commercial/transactional/navigational)
- Target Keyword: Identify primary keyword and variations
- Keyword Density & Clustering (NEW!): Deep analysis of keyword density, distribution heatmap, topic clustering, and keyword stuffing risk detection
- Keyword Placement: Check H1, H2, first 100 words, meta title/description
- Heading Structure: Evaluate H1-H6 hierarchy and keyword integration
- Content Length Comparison (NEW!): Compare word count against top 10-20 SERP competitors to determine optimal length
- Meta Elements: Review meta title (50-60 chars) and description (150-160 chars)
- Internal Links: Count and evaluate quality of internal links (aim for 3-5+)
- External Links: Check for authoritative external sources
- Readability Score (NEW!): Calculate Flesch Reading Ease, Flesch-Kincaid Grade Level, passive voice ratio, sentence complexity
- SEO Quality Rating (NEW!): Overall score (0-100) with category breakdowns for content, keywords, meta, structure, links, and readability
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.
- 5d ago First seen · 119 lines · 0 tokens per session scan A 48de4b4b22ca
analyze-existing is a command published in the GitHub repository seite-sh/seite (20 stars, last pushed 21d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,309 tokens. A static security scan graded it A with 0 findings. It is 98% identical to analyze-existing, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
awesome-chatgpt
Search awesome-ChatGPT-repositories for open-source GitHub repositories related to ChatGPT and LLMs.
init
Scaffold a new MindBase project (v2 layout). Usage: /mb:init [template] [-- mission ...].
commit
智能生成 Git 提交信息并提交.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
doctor.es
Diagnostica problemas de inferencia LLM en Mac: asiai doctor verifica el estado de los motores, conflictos de puertos, carga de modelos y estado de la GPU.
claude-request
Send a prompt to Claude Code via the LLM gateway with session tracking.