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 o2alexanderfedin/strategic-research-automation-template --skill comparative-analyzergit clone --depth 1 https://github.com/o2alexanderfedin/strategic-research-automation-templateWrote 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/o2alexanderfedin/strategic-research-automation-template/comparative-analyzer)<a href="https://agentmods.dev/skills/o2alexanderfedin/strategic-research-automation-template/comparative-analyzer"><img src="https://agentmods.dev/badge/skills/o2alexanderfedin/strategic-research-automation-template/comparative-analyzer/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/o2alexanderfedin/strategic-research-automation-template/comparative-analyzer"><img src="https://agentmods.dev/badge/skills/o2alexanderfedin/strategic-research-automation-template/comparative-analyzer.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.00000 | $0.03423 |
| Opus 5 | $0.00000 | $0.01711 |
| Sonnet 5 | $0.00000 | $0.00685 |
| Haiku 4.5 | $0.00000 | $0.00342 |
Grade A, and why
comparative-analyzer 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.
How it starts
The opening of the file, as written. The whole thing — 457 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: "comparative-analyzer" description: | Performs cross-sprint comparative analysis to rank opportunities, identify patterns, and recommend prioritization. Activates when: comparing multiple sprints, ranking opportunities, analyzing portfolio strategy, identifying cross-opportunity patterns, recommending execution sequences, or allocating resources across opportunities. Generates strategic insights spanning multiple opportunities with investment allocation and prioritization recommendations. allowed-tools:
- Read
- Write
- Grep
- Glob
Comparative Analyzer Skill
Role
You are the Comparative Analyzer, responsible for performing cross-sprint comparative analysis to rank opportunities, identify patterns, and recommend strategic prioritization.
Core Responsibilities
1. Multi-Sprint Data Aggregation
Objective: Collect and organize data from all completed sprints
Process:
- Use Glob to find all sprint reports:
glob "reports/sprint-*-report.md" - Use Read to load each report
- Extract key data points:
- Opportunity name
- Final score (0-100)
- Dimensional scores (market, technical, competitive, execution, regulatory)
- Recommendation tier (STRONG GO / GO / CONDITIONAL GO / NO GO)
- TAM/SAM/SOM values
- Timeline estimates (POC, prototype, certification)
- Investment requirements
- Key differentiators
- Critical risks
- Organize data in structured format (table or matrix)
Data Structure:
Sprint_ID | Name | Score | Market | Technical | Competitive | Execution | Regulatory | TAM | SOM | Timeline | Investment | Tier
01 | Weather Decisions | 87 | 85 | 82 | 88 | 75 | 80 | $2.8B | $85M | 3yr | $2M-$4M | STRONG GO
02 | Collision Avoidance | 83 | 80 | 85 | 82 | 78 | 77 | $3.0B | $90M | 3.5yr | $6M-$11M | GO
...
2. Comparative Scoring Analysis
Objective: Compare opportunities across scoring dimensions
Analyses to Perform:
A. Overall Score Ranking
- Sort opportunities by final score (descending)
- Identify score distribution (how spread out scores are)
- Identify natural tiers (e.g., 80+, 65-79, 50-64)
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 · 457 lines · 0 tokens per session scan A 37454073b677
comparative-analyzer is a skill published in the GitHub repository o2alexanderfedin/strategic-research-automation-template (19 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,423 tokens. 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-30.
Other skills, from other repositories
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment.
cmux
This skill should be used when the user invokes /cmux or asks to spawn parallel Claude Code sessions in cmux terminal panes, monitor agent output, automate browsers in cmux, manage cmux notifications, or perform any cmux terminal management task. Requires CMUXSOCKETPATH environment variable to be set.
api-design
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
coding-standards
Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.
frontend-patterns
Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.