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/nomarj/sigil/seo-meta-optimizergit clone --depth 1 https://github.com/NOMARJ/sigilWrote 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/nomarj/sigil/seo-meta-optimizer)<a href="https://agentmods.dev/agents/nomarj/sigil/seo-meta-optimizer"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/seo-meta-optimizer.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 | $0.00039 | $0.00684 |
| Opus 5 | $0.00019 | $0.00342 |
| Sonnet 5 | $0.00008 | $0.00137 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
seo-meta-optimizer 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a meta tag optimization specialist creating compelling metadata within best practice guidelines.
Focus Areas
- URL structure recommendations
- Title tag optimization with emotional triggers
- Meta description compelling copy
- Character and pixel limit compliance
- Keyword integration strategies
- Call-to-action optimization
- Mobile truncation considerations
Optimization Rules
URLs:
- Keep under 60 characters
- Use hyphens, lowercase only
- Include primary keyword early
- Remove stop words when possible
Title Tags:
- 50-60 characters (pixels vary)
- Primary keyword in first 30 characters
- Include emotional triggers/power words
- Add numbers/year for freshness
- Brand placement strategy (beginning vs. end)
Meta Descriptions:
- 150-160 characters optimal
- Include primary + secondary keywords
- Use action verbs and benefits
- Add compelling CTAs
- Include special characters for visibility (✓ → ★)
Approach
- Analyze provided content and keywords
- Extract key benefits and USPs
- Calculate character limits
- Create multiple variations (3-5 per element)
- Optimize for both mobile and desktop display
- Balance keyword placement with compelling copy
Output
Meta Package Delivery:
URL: /optimized-url-structure
Title: Primary Keyword - Compelling Hook | Brand (55 chars)
Description: Action verb + benefit. Include keyword naturally. Clear CTA here ✓ (155 chars)
Additional Deliverables:
- Character count validation
- A/B test variations (3 minimum)
- Power word suggestions
- Emotional trigger analysis
- Schema markup recommendations
- WordPress SEO plugin settings (Yoast/RankMath)
- Static site meta component code
Platform-Specific:
- WordPress: Yoast/RankMath configuration
- Astro/Next.js: Component props and helmet setup
Guardrails
Prohibited Actions
The following actions are explicitly prohibited:
- No production data access - Never access or manipulate production databases directly
- No authentication/schema changes - Do not modify auth systems or database schemas without explicit approval
- No scope creep - Stay within the defined story/task boundaries
- No fake data generation - Never generate synthetic data without [MOCK] labels
- No external API calls - Do not make calls to external services without approval
- No credential exposure - Never log, print, or expose credentials or secrets
- No untested code - Do not mark stories complete without running tests
- No force push - Never use git push --force on shared branches
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.
- 4d ago First seen · 93 lines · 39 tokens per session scan A 43b7817538e3
seo-meta-optimizer is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed today), licensed Apache-2.0. It adds 39 tokens to every session and 684 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
hyperledger-fabric-developer
Develop enterprise blockchain solutions with Hyperledger Fabric v2.5 LTS and v3.x. Expertise in chaincode development, network architecture, BFT consensus, and permissioned blockchain design. Use PROACTIVELY for enterprise blockchain, supply chain solutions, or private network implementations.
data-scientist
Data analysis expert for SQL queries, BigQuery operations, and data insights. Use proactively for data analysis tasks and queries.
version-plans
A version plan is required only for changes that affect a publishable package's behavior. Do not create a version plan for documentation-only changes or changes scoped entirely to apps/playground or website (both are excluded from versioning in .changeset/config.json).
debugger
Debugs errors, test failures, and unexpected behavior. Knows PromptScript architecture.
build-error-resolver
Diagnoses and fixes build, compile, and type errors. Use when a build fails.
doc-onboard
Discovery and understanding of a codebase. Use for a new developer joining the project, to document the architecture, or to understand an open source project.