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 skills add indranilbanerjee/neels-plugins --skill competitor-pagesgit clone --depth 1 https://github.com/indranilbanerjee/neels-pluginsWrote 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/skills/indranilbanerjee/neels-plugins/competitor-pages)<a href="https://agentmods.dev/skills/indranilbanerjee/neels-plugins/competitor-pages"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/neels-plugins/competitor-pages/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/skills/indranilbanerjee/neels-plugins/competitor-pages"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/neels-plugins/competitor-pages.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.00028 | $0.01872 |
| Opus 5.5 | $0.00011 | $0.00749 |
| Sonnet 5.5 | $0.00006 | $0.00374 |
| Haiku 4.5 | $0.00003 | $0.00187 |
Grade A, and why
competitor-pages 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
88% identical to competitor-pages — 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/digital-marketing-pro:competitor-pages
Purpose
Create high-converting competitor comparison and alternatives pages that target competitive intent keywords with accurate, structured content and appropriate schema markup.
Input Required
The user must provide (or will be prompted for):
- Page type: "X vs Y", "alternatives to X", "best tools roundup", or "comparison table"
- Your product/service: The product being positioned
- Competitors: 1-5 competitor products to compare against
- Comparison criteria: Features, pricing, use cases to compare (or auto-detected)
- Target audience: Who is making this purchase decision
Page Types
1. "X vs Y" Comparison Pages
- Direct head-to-head comparison between two products/services
- Balanced feature-by-feature analysis
- Clear verdict or recommendation with justification
- Target keyword:
[Product A] vs [Product B]
2. "Alternatives to X" Pages
- List of alternatives to a specific product/service
- Each alternative with brief summary, pros/cons, best-for use case
- Target keyword:
[Product] alternatives,best alternatives to [Product]
3. "Best [Category] Tools" Roundup Pages
- Curated list of top tools/services in a category
- Ranking criteria clearly stated
- Target keyword:
best [category] tools [year],top [category] software
4. Comparison Table Pages
- Feature matrix with multiple products in columns
- Sortable/filterable layout recommendations
- Target keyword:
[category] comparison,[category] comparison chart
Process
- Load brand context: Read
~/.claude-marketing/brands/_active-brand.jsonfor the active slug, then load~/.claude-marketing/brands/{slug}/profile.json. Apply brand voice and compliance rules. Check for brand guidelines — especially restrictions on competitor mentions. - Research competitors: Gather feature data, pricing, positioning from public sources. Verify all claims.
- Generate comparison structure: Feature matrix, content outline, section order
- Apply schema markup: Product, SoftwareApplication, or ItemList JSON-LD depending on page type (via
schema-generator.py --type <Type>—AggregateRatingis not a standalone--type; it is a nested field insideProduct, as shown in the Product template below) - Optimize for conversion: CTA placement strategy, social proof sections, pricing highlights
- Apply fairness guidelines: Accuracy verification, source citations, affiliation disclosure
- Keyword optimization: Primary and secondary keyword targeting, title tag formulas, H1 patterns
- Internal linking strategy: Cross-link between related comparison pages, feature pages, case studies
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 · 195 lines · 28 tokens per session scan A 522d52d44e0b
competitor-pages is a skill published in the GitHub repository indranilbanerjee/neels-plugins (6 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 1,872 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to competitor-pages, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
continuous-improvement-loop
Run the Part 12 continuous improvement loop into a quarterly brief for leadership. "produce the quarterly improvement brief".
yearly-planner
Produce the Part 8 yearly planner: quarterly themes and monthly initiatives. "plan the whole year month by month".
attribution-report
Run attribution on real conversion paths, comparing models. "which channels actually drive revenue".
validate-output
Validate content structure against a schema: sections, word counts. "scan for leftover placeholders".
add-integration
Add a custom MCP integration: scaffold the server, write .mcp.json, test it. "add a new MCP server".
client-proposal
Draft a client proposal or RFP response: scope, deliverables, KPIs, pricing tiers. "respond to this RFP".