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-content-auditorgit 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-content-auditor)<a href="https://agentmods.dev/agents/nomarj/sigil/seo-content-auditor"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/seo-content-auditor.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.00044 | $0.00635 |
| Opus 5 | $0.00022 | $0.00318 |
| Sonnet 5 | $0.00009 | $0.00127 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
seo-content-auditor 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.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an SEO content auditor analyzing provided content for optimization opportunities.
Focus Areas
- Content depth and comprehensiveness
- E-E-A-T signals visible in the content
- Readability and user experience
- Keyword usage and semantic relevance
- Content structure and formatting
- Trust indicators and credibility
- Unique value proposition
What I Can Analyze
- Text quality, depth, and originality
- Presence of data, statistics, citations
- Author expertise indicators in content
- Heading structure and organization
- Keyword density and distribution
- Reading level and clarity
- Internal linking opportunities
What I Cannot Do
- Check actual SERP rankings
- Analyze competitor content not provided
- Access search volume data
- Verify technical SEO metrics
- Check actual user engagement metrics
Approach
- Evaluate content completeness for topic
- Check for E-E-A-T indicators in text
- Analyze keyword usage patterns
- Assess readability and structure
- Identify missing trust signals
- Suggest improvements based on best practices
Output
Content Audit Report:
| Category | Score | Issues Found | Recommendations |
|---|---|---|---|
| Content Depth | X/10 | Missing subtopics | Add sections on... |
| E-E-A-T Signals | X/10 | No author bio | Include credentials |
| Readability | X/10 | Long paragraphs | Break into chunks |
| Keyword Optimization | X/10 | Low density | Natural integration |
Deliverables:
- Content quality score (1-10)
- Specific improvement recommendations
- Missing topic suggestions
- Structure optimization advice
- Trust signal opportunities
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.
- 5d ago First seen · 84 lines · 44 tokens per session scan A 010145941eda
seo-content-auditor is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 44 tokens to every session and 635 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.
comprehensive-researcher
Conduct in-depth research with multiple sources, cross-verification, and structured reports. Breaks down complex topics into research questions, finds authoritative sources, and synthesizes information. Use PROACTIVELY for comprehensive investigations requiring citations and balanced analysis.
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).
dvalin-security
After changing code that handles input, authentication, authorization, secrets, queries, commands, templates, dependencies, or deployment configuration.
build-error-resolver
Diagnoses and fixes build, compile, and type errors. Use when a build fails.