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 tahirraufkeeyu/software-development-agent-stack--sdas --skill competitor-monitorgit clone --depth 1 https://github.com/tahirraufkeeyu/software-development-agent-stack--sdasWrote 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/tahirraufkeeyu/software-development-agent-stack--sdas/competitor-monitor)<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/competitor-monitor"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/competitor-monitor/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/tahirraufkeeyu/software-development-agent-stack--sdas/competitor-monitor"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/competitor-monitor.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.00058 | $0.02694 |
| Opus 5 | $0.00029 | $0.01347 |
| Sonnet 5 | $0.00012 | $0.00539 |
| Haiku 4.5 | $0.00006 | $0.00269 |
Grade A, and why
competitor-monitor 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 12d 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
Trigger this skill when the request includes any of:
- "Run the weekly competitor digest"
- "What did [competitor] ship this week?"
- "Did pricing change on any of our competitors?"
- "Summarize what's new across our competitive set"
- A scheduled Monday-morning job
Do not use for deep one-off competitor teardowns (that is a separate analyst engagement), win/loss analysis (sales-led), or feature-by-feature comparison tables (use content-writer with the competitor data as input).
Inputs
Required:
- Competitor list — 3-8 named competitors with URLs for: blog, newsroom/changelog, pricing page, and primary LinkedIn account.
- Our category — so the skill can judge what matters vs what is noise.
Optional:
- Previous digest — the last weekly output. Enables week-over-week diff framing.
- Focus areas — e.g., "we especially care about pricing changes and enterprise positioning."
- Cadence override — defaults to weekly (Monday 9am); biweekly or monthly can be requested.
Outputs
A single dated digest with these sections:
- Header — week range (e.g., "Week of 2026-04-13 to 2026-04-19"), competitors tracked, and a one-line executive summary.
- New content — per competitor, 1-3 bullet summaries of new blog posts, case studies, whitepapers, or videos shipped this week. Each with URL and publish date.
- Positioning shifts — any change in homepage hero, tagline, category claim, or messaging hierarchy vs the previous snapshot.
- Pricing changes — added/removed tiers, price deltas, new add-ons, changes to free tier or trial length.
- Product moves — launches, major feature additions, integrations, deprecations, public beta announcements.
- Social / executive signal — notable posts from competitor CEOs, heads of product, or official company accounts (LinkedIn and X).
- Our recommended response — for each signal that matters, a specific action: update comparison page, draft rebuttal post, brief sales, ignore, or escalate.
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.
- 12d ago First seen · 247 lines · 58 tokens per session scan A 0dc849c88b9b
competitor-monitor is a skill published in the GitHub repository tahirraufkeeyu/software-development-agent-stack--sdas (18 stars, last pushed 4mo ago), licensed MIT. It adds 58 tokens to every session and 2,694 once invoked, about $0.0003 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…