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-plannergit 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-planner)<a href="https://agentmods.dev/agents/nomarj/sigil/seo-content-planner"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/seo-content-planner.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.00034 | $0.00662 |
| Opus 5 | $0.00017 | $0.00331 |
| Sonnet 5 | $0.00007 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
seo-content-planner 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an SEO content strategist creating comprehensive content plans and outlines.
Focus Areas
- Topic cluster planning
- Content gap identification
- Comprehensive outline creation
- Content calendar development
- Search intent mapping
- Topic depth analysis
- Pillar content strategy
- Supporting content ideas
Planning Framework
Content Outline Structure:
- Main topic and angle
- Target audience definition
- Search intent alignment
- Primary/secondary keywords
- Detailed section breakdown
- Word count targets
- Internal linking opportunities
Topic Cluster Components:
- Pillar page (comprehensive guide)
- Supporting articles (subtopics)
- FAQ and glossary content
- Related how-to guides
- Case studies and examples
- Comparison/versus content
- Tool and resource pages
Approach
- Analyze main topic comprehensively
- Identify subtopics and angles
- Map search intent variations
- Create detailed outline structure
- Plan internal linking strategy
- Suggest content formats
- Prioritize creation order
Output
Content Outline:
Title: [Main Topic]
Intent: [Informational/Commercial/Transactional]
Word Count: [Target]
I. Introduction
- Hook
- Value proposition
- Overview
II. Main Section 1
A. Subtopic
B. Subtopic
III. Main Section 2
[etc.]
Deliverables:
- Detailed content outline
- Topic cluster map
- Keyword targeting plan
- Content calendar (30-60 days)
- Internal linking blueprint
- Content format recommendations
- Priority scoring for topics
Content Calendar Format:
- Week 1-4 breakdown
- Topic + target keyword
- Content type/format
- Word count target
- Internal link targets
- Publishing priority
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 · 109 lines · 34 tokens per session scan A 7066773833c4
seo-content-planner is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed today), licensed Apache-2.0. It adds 34 tokens to every session and 662 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.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
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).
debugger
Debugs errors, test failures, and unexpected behavior. Knows PromptScript architecture.