Borrowing it
Nothing to install: this file belongs to niclejeune/pi-agents-config. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/niclejeune/pi-agents-config/main/.pi/agent/skills/seo-competitor-pages/SKILL.mdgit clone --depth 1 https://github.com/niclejeune/pi-agents-configWrote 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/niclejeune/pi-agents-config/seo-competitor-pages)<a href="https://agentmods.dev/skills/niclejeune/pi-agents-config/seo-competitor-pages"><img src="https://agentmods.dev/badge/skills/niclejeune/pi-agents-config/seo-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/niclejeune/pi-agents-config/seo-competitor-pages"><img src="https://agentmods.dev/badge/skills/niclejeune/pi-agents-config/seo-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.00070 | $0.01648 |
| Opus 5 | $0.00035 | $0.00824 |
| Sonnet 5 | $0.00014 | $0.00330 |
| Haiku 4.5 | $0.00007 | $0.00165 |
Grade A, and why
seo-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 11d 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
92% identical to seo-competitor-pages — 24 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitor Comparison & Alternatives Pages
Create high-converting comparison and alternatives pages that target competitive intent keywords with accurate, structured content.
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 if interactive
- Target keyword:
[category] comparison,[category] comparison chart
Comparison Table Generation
Feature Matrix Layout
| Feature | Your Product | Competitor A | Competitor B |
|------------------|:------------:|:------------:|:------------:|
| Feature 1 | ✅ | ✅ | ❌ |
| Feature 2 | ✅ | ⚠️ Partial | ✅ |
| Feature 3 | ✅ | ❌ | ❌ |
| Pricing (from) | $X/mo | $Y/mo | $Z/mo |
| Free Tier | ✅ | ❌ | ✅ |
Data Accuracy Requirements
- All feature claims must be verifiable from public sources
- Pricing must be current (include "as of [date]" note)
- Update frequency: review quarterly or when competitors ship major changes
- Link to source for each competitor data point where possible
Schema Markup Recommendations
Product Schema with AggregateRating
{
"@context": "https://schema.org",
"@type": "Product",
"name": "[Product Name]",
"description": "[Product Description]",
"brand": {
"@type": "Brand",
"name": "[Brand Name]"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "[Rating]",
"reviewCount": "[Count]",
"bestRating": "5",
"worstRating": "1"
}
}
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.
- 11d ago First seen · 205 lines · 70 tokens per session scan A 620e5ce33b10
seo-competitor-pages is a skill published in the GitHub repository niclejeune/pi-agents-config (1 stars, last pushed 4mo ago), licensed MIT. It adds 70 tokens to every session and 1,648 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to seo-competitor-pages, differing in 24 lines, and is treated as a copy.
Other skills, from other repositories
exa-research-planner
Plan, draft, and execute Exa deep-research workflows. Use when the user wants staged research planning, cost-aware discovery before deep synthesis, or an explicit deep-research report. Also use when the user asks to refine a research question, compare options, explore a market or technical landscape, gather sources…
brpr
(devtools plugin) Create a branch, commit changes, push, and open a PR — or just commit+push+PR if already on a feature branch. Links related issues from GitHub or Linear based on project tracker config.
workspace-explorer
Explore and navigate Notion workspaces via MCP. Use when searching for pages, understanding database structure, finding content, creating or updating pages/databases, or managing Notion workspace content. Triggers when user asks about Notion, mentions Notion pages/databases, wants to find something in their wiki…
merge
Merge or squash-merge a pull request and report best-effort remote and local source-branch cleanup. Use when user says "merge this PR", "squash merge", "md", "smd", or anything about merging pull requests.
release
Automate the release process. Use when user says "cut a release", "new version", "bump version", "publish release", or anything about versioning and publishing.
setup-oauth
Guide the user through setting up Notion MCP with OAuth authentication.