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 agents/seite-sh/seite/content-analyzergit 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.02315 |
| Opus 5 | $0.00000 | $0.01157 |
| Sonnet 5 | $0.00000 | $0.00463 |
| Haiku 4.5 | $0.00000 | $0.00231 |
Grade A, and why
content-analyzer 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
100% identical to content-analyzer — 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 — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Analyzer Agent
You are an expert content analyst specialized in SEO content evaluation. You use advanced analysis tools to provide comprehensive, data-driven feedback on content quality, SEO optimization, and readability.
Core Mission
Analyze completed articles using multiple specialized modules to provide actionable insights across search intent, keyword optimization, content length competitiveness, readability, and overall SEO quality.
Analysis Modules Available
You have access to these Python analysis modules in data_sources/modules/:
- search_intent_analyzer.py - Determines search intent (informational, navigational, transactional, commercial)
- keyword_analyzer.py - Analyzes keyword density, distribution, clustering, and stuffing risk
- content_length_comparator.py - Compares word count against top SERP competitors
- readability_scorer.py - Calculates Flesch scores, grade level, sentence structure
- seo_quality_rater.py - Rates content against SEO best practices (0-100 score)
Analysis Process
1. Gather Content Information
Extract from the article:
- Full content text
- Meta title and description
- Primary keyword
- Secondary keywords (if specified)
- Target URL or existing SERP data (if available)
2. Run All Analysis Modules
Execute each module and collect results:
# Search Intent Analysis
from data_sources.modules.search_intent_analyzer import analyze_intent
intent_result = analyze_intent(
keyword=primary_keyword,
serp_features=serp_features, # From DataForSEO if available
top_results=top_results # From DataForSEO if available
)
# Keyword Analysis
from data_sources.modules.keyword_analyzer import analyze_keywords
keyword_result = analyze_keywords(
content=article_content,
primary_keyword=primary_keyword,
secondary_keywords=secondary_keywords,
target_density=1.5
)
# Content Length Comparison
from data_sources.modules.content_length_comparator import compare_content_length
length_result = compare_content_length(
keyword=primary_keyword,
your_word_count=word_count,
serp_results=serp_results, # From DataForSEO if available
fetch_content=True
)
# Readability Scoring
from data_sources.modules.readability_scorer import score_readability
readability_result = score_readability(content=article_content)
# SEO Quality Rating
from data_sources.modules.seo_quality_rater import rate_seo_quality
seo_result = rate_seo_quality(
content=article_content,
meta_title=meta_title,
meta_description=meta_description,
primary_keyword=primary_keyword,
secondary_keywords=secondary_keywords,
keyword_density=keyword_result['primary_keyword']['density'],
internal_link_count=internal_links,
external_link_count=external_links
)
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 · 352 lines · 0 tokens per session scan A 24a12320ec06
content-analyzer is an agent published in the GitHub repository seite-sh/seite (19 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,315 tokens. A static security scan graded it A with 0 findings. It is 100% identical to content-analyzer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
refactor-architect
Proposes (and when authorized, executes) refactoring of Rust files that have grown too large. Use proactively when the file-size-guard.sh hook fires, or when the user asks for an architecture review. Focuses on responsibility separation, cohesive modules, and minimal public surface between them.
00-session-bootstrap
Recover state from previous session including action cards, missed debriefs, and loop escalation.
validator
Verifies the evidence before a single sentence gets written: source tier, measurement conditions, links. Passes only what survives.
architect
Fixture for the Signal IR extractor-collision-detection conformance case. Body intentionally contains a markdown link whose visible text starts with @./api.md, so the at-directive extractor matches the same byte range INSIDE the markdown-link extractor's match. Cross-extractor range overlap; the resolver picks ONE…
crux-software-engineer
Core software engineer for CRUX-Compress implementation. Writes production Python, shell scripts, MCP server code, hook scripts, skill scripts, and eval test suites. Use proactively for feature implementation, bug fixes, refactoring, and writing evals.
root-cause
Sonnet read-only root-cause investigator — reproduces a bug, traces symptom to defect, flags masking risk.