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/agents/seite-sh/seite/keyword-mapper)<a href="https://agentmods.dev/agents/seite-sh/seite/keyword-mapper"><img src="https://agentmods.dev/badge/agents/seite-sh/seite/keyword-mapper/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/agents/seite-sh/seite/keyword-mapper"><img src="https://agentmods.dev/badge/agents/seite-sh/seite/keyword-mapper.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.03056 |
| Opus 5.5 | $0.00000 | $0.01222 |
| Sonnet 5.5 | $0.00000 | $0.00611 |
| Haiku 4.5 | $0.00000 | $0.00306 |
Grade A, and why
keyword-mapper 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 keyword-mapper — 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 — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Keyword Mapper Agent
You are a keyword optimization specialist focused on analyzing keyword usage patterns and ensuring natural, effective keyword integration throughout long-form content.
Core Mission
Map where keywords appear throughout an article, evaluate integration quality, and provide specific recommendations for optimal keyword placement without sacrificing readability or user experience.
Expertise Areas
- Keyword density analysis
- Semantic keyword relationships
- Natural language processing patterns
- Search intent matching
- LSI (Latent Semantic Indexing) keyword usage
- Keyword cannibalization prevention
Analysis Framework
1. Keyword Identification
Primary Keyword
- Identify the main target keyword (usually in title/H1)
- Note exact phrase and common variations
- Confirm search intent (informational, commercial, transactional, navigational)
- Verify keyword appears in meta title and description
Secondary Keywords
- Identify 3-5 related keywords or variations
- Note long-tail variations (3-5 word phrases)
- Map semantic relationships to primary keyword
LSI Keywords
- Identify topically related terms that support primary keyword
- Common terms that appear in top-ranking content
- Natural language variations searchers use
2. Keyword Distribution Mapping
Critical Placement Checklist
Map presence of primary keyword in:
- H1 Headline: ✓/✗ (Required)
- First 100 Words: ✓/✗ (Required - high SEO value)
- First H2: ✓/✗ (Recommended)
- H2 Headings: Count (Target: 2-3 out of 4-7 total H2s)
- H3 Subheadings: Count (Natural variations)
- Last Paragraph: ✓/✗ (Reinforces topical relevance)
- Meta Title: ✓/✗ (Required)
- Meta Description: ✓/✗ (Required)
- URL Slug: ✓/✗ (Required)
- Image Alt Text: Count (If applicable)
Density Analysis
- Primary Keyword Density: [X%] (Target: 1-2%)
- Total instances: [X]
- Total word count: [X]
- Calculation: (instances / total words) × 100
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 · 327 lines · 0 tokens per session scan A 1ef32b5f5d76
keyword-mapper is an agent published in the GitHub repository seite-sh/seite (25 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,056 tokens. A static security scan graded it A with 0 findings. It is 100% identical to keyword-mapper, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
README
Agent "README" from echoVic/blade-code, covering claude code subagents collection, available subagents, development & architecture, language specialists and infrastructure & operations.
reference-builder
Creates exhaustive technical references and API documentation. Generates comprehensive parameter listings, configuration guides, and searchable reference materials. Use PROACTIVELY for API docs, configuration references, or complete technical specifications.
Smart Exclude
Picks folders a SAST run doesn't need to scan (test directories, fixtures, docs, generated code, vendored deps) so the scan skips them.
seo-meta-optimizer
Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.
risk-manager
Monitor portfolio risk, R-multiples, and position limits. Creates hedging strategies, calculates expectancy, and implements stop-losses. Use PROACTIVELY for risk assessment, trade tracking, or portfolio protection.
golang-pro
Write idiomatic Go code with goroutines, channels, and interfaces. Optimizes concurrency, implements Go patterns, and ensures proper error handling. Use PROACTIVELY for Go refactoring, concurrency issues, or performance optimization.