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 yutori-ai/yutori-mcp --skill 04-competitor-watchgit clone --depth 1 https://github.com/yutori-ai/yutori-mcpWrote 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/yutori-ai/yutori-mcp/04-competitor-watch)<a href="https://agentmods.dev/skills/yutori-ai/yutori-mcp/04-competitor-watch"><img src="https://agentmods.dev/badge/skills/yutori-ai/yutori-mcp/04-competitor-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/yutori-ai/yutori-mcp/04-competitor-watch"><img src="https://agentmods.dev/badge/skills/yutori-ai/yutori-mcp/04-competitor-watch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00030 | $0.00389 |
| Opus 5 | $0.00015 | $0.00195 |
| Sonnet 5 | $0.00006 | $0.00078 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
yutori-competitor-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 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.
What it actually says
Competitor Monitoring Setup
Set up comprehensive monitoring for a competitor.
Create a scout with this query structure:
**Context:** Monitoring competitive intelligence for $ARGUMENTS
## What to Monitor
- **News & Announcements:** Press releases, media coverage, blog posts
- **Product Updates:** New features, pricing changes, product launches
- **Funding & Business:** Funding rounds, acquisitions, partnerships, executive changes
- **Public Communications:** Social media announcements, conference talks, webinars
**Sources to check:** TechCrunch, company blog, LinkedIn, Twitter/X, Crunchbase, press releases
**Exclusions:** Job postings (unless executive level), routine social media, unverified rumors
## Deliverables
**Frequency:** Daily
**Output format:**
1. Summary of significant developments (if any)
2. Table of news items with: Date, Headline, Category, Source Link
3. Analysis of competitive implications
Use create_scout with:
query: The above structured query with $ARGUMENTS replacedoutput_interval: 86400 (daily)
After creation, inform the user:
- Scout will run daily and email results
- They can check updates anytime with
get_scout_updates - They can pause/resume with
edit_scout
Fetching documentation or source URLs:
If you use a web fetch tool to look up the competitor's blog, docs, or other pages while preparing the query, include the Accept: text/markdown header. Many documentation sites (Cloudflare-hosted) will return clean Markdown instead of HTML — fewer tokens, easier to parse.
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 · 47 lines · 30 tokens per session scan A ec0a3db643c0
yutori-competitor-watch is a skill published in the GitHub repository yutori-ai/yutori-mcp (24 stars, last pushed today), licensed Apache-2.0. It adds 30 tokens to every session and 389 once invoked, about $0.0002 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
site-audit
Use when user asks to audit a website, review all pages, check for broken links, capture full site state, or do a comprehensive product review.
kaboom
Use when user asks to check browser state, debug page errors, inspect network traffic, take screenshots, automate clicks or form fills, run accessibility or security audits, measure performance, generate tests, or record browser sessions. Trigger phrases: "check my browser", "debug this page", "take a screenshot"…
kaboom-connection-guard
Use when a tool call fails with "extension not connected", the daemon is unreachable, or browser telemetry stops arriving.
audit
Use when the user wants a full Kaboom quality audit of a web app or tracked site, with one polished report covering Functionality, UX Polish, Accessibility, Performance, Release Risk, and SEO.
api-validation
Use when user asks to check API responses, validate request/response contracts, compare API behavior against a spec, or detect schema drift.
automate
Use when user asks to automate browser actions, click buttons, fill forms, navigate pages, run a sequence of browser steps, or build a repeatable workflow.