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 TommyBez/evex --skill competitor-intel-watchgit clone --depth 1 https://github.com/TommyBez/evexWrote 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/tommybez/evex/competitor-intel-watch)<a href="https://agentmods.dev/skills/tommybez/evex/competitor-intel-watch"><img src="https://agentmods.dev/badge/skills/tommybez/evex/competitor-intel-watch/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/tommybez/evex/competitor-intel-watch"><img src="https://agentmods.dev/badge/skills/tommybez/evex/competitor-intel-watch.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.00025 | $0.00412 |
| Opus 5.5 | $0.00010 | $0.00165 |
| Sonnet 5.5 | $0.00005 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
competitor-intel-watch 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 1mo 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.
What it actually says
Use this skill on every scheduled watch and any chat request to run the monitor.
Order of work
- Call
load_watch_config. The URL list and thresholds come from environment variables and an optional config file. Never invent a URL. - Fetch each listed URL with
fetch_competitor_page. That tool loads{origin}/robots.txtfirst and skips the page when robots disallows this user-agent or when robots.txt cannot be reached. - Diff each successful fetch with
diff_page_snapshot. A first-seen URL is a committed baseline, score 0, not an alert. Threshold-clearing changes stay pending in the store untilsend_digestdelivers. - Deliver only rows where
clearsThresholdis true. Bothscore >= COMPETITOR_INTEL_ALERT_MIN_SCOREandchangedChars >= COMPETITOR_INTEL_ALERT_MIN_CHANGED_CHARSmust pass. The score isround(100 * changedChars / max(beforeLength, afterLength, 1)), capped at 100. Do not invent another metric. - Preview with
preview_digest, then send withsend_digestonly whenconfirmSendis true and you reuse theidempotencyKeyandrunDatereturned bypreview_digest.send_digestalways pauses for Eve human approval before Slack or Resend.
Hard stops
- Empty watch list or missing delivery config: report
missingEnvand stop. blockedByRobots: skip that URL. Do not retry with a different user-agent.- No threshold-clearing changes: do not call
send_digest. send_digestwithoutconfirmSend=true: the tool refuses. Review the preview first. Approval is a separate Eve pause.sent: falsewith an error: the digest was not delivered. Do not claim it was sent.
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.
- 1mo ago First seen · 23 lines · 25 tokens per session scan A 0148d723a5e0
competitor-intel-watch is a skill published in the GitHub repository TommyBez/evex (25 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 412 once invoked, about $0.0001 per session on Opus 5.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-09-09.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…