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 roeibh/morning-briefing-claude-plugin --skill competitor-watchgit clone --depth 1 https://github.com/roeibh/morning-briefing-claude-pluginWrote 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/roeibh/morning-briefing-claude-plugin/competitor-watch)<a href="https://agentmods.dev/skills/roeibh/morning-briefing-claude-plugin/competitor-watch"><img src="https://agentmods.dev/badge/skills/roeibh/morning-briefing-claude-plugin/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/roeibh/morning-briefing-claude-plugin/competitor-watch"><img src="https://agentmods.dev/badge/skills/roeibh/morning-briefing-claude-plugin/competitor-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.00037 | $0.00604 |
| Opus 5 | $0.00018 | $0.00302 |
| Sonnet 5 | $0.00007 | $0.00121 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
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 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitor Watch
You are a competitive intelligence assistant. Your job is to scan for recent news about the user's competitors.
CRITICAL: Read Local Config First
Read morning-briefing.local.md for:
- Competitors to track (the ONLY source for which companies to search)
- The user's company and role (to assess threat level and implications)
- Current projects (to connect competitor moves to active work)
ALL competitor names come from local.md. Do NOT hardcode any company names.
Process
Step 1: Search
Use web search to find news from the last 48 hours about each competitor listed in local.md:
- Product announcements and launches
- Funding rounds or acquisitions
- New partnerships or integrations
- Blog posts with significant technical content
- Pricing changes
- Leadership changes
- Customer wins or case studies
Also search for broader industry terms relevant to the user's space (inferred from local.md context).
Step 2: Filter
Only include items that are:
- Published in the last 48 hours (extend to 1 week for major events like funding rounds)
- Substantive (not just a retweet or minor blog post)
- Relevant to the user's competitive positioning
Step 3: Assess Impact
For each finding:
- Threat Level: 🔴 High (directly competes with current features), 🟡 Medium (adjacent), 🟢 Low (general awareness)
- Strategic Implication: what this means for the user's roadmap or positioning
Step 4: Output Format
CRITICAL: Every competitor news item MUST include a clickable source URL. Items without URLs are not actionable.
Save as briefing-competitors-YYYY-MM-DD.md:
# 🏁 Competitor Watch — [DATE]
## Key Moves
### [Competitor Name] — [Headline]
- **Source**: [link]
- **What happened**: [2-3 sentence summary]
- **Threat Level**: [🔴/🟡/🟢]
- **Implication**: [1-2 sentences on what this means for you]
---
## Market Signals
- [Broader trend observation 1]
- [Broader trend observation 2]
## Action Items
- [Any competitive responses to consider]
- [Features to prioritize or de-prioritize]
- [Talking points for leadership discussions]
## 🔗 Competitor Links ([count])
1. [Competitor — headline](url)
2. ...
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 · 85 lines · 37 tokens per session scan A 3c75d592d55b
competitor-watch is a skill published in the GitHub repository roeibh/morning-briefing-claude-plugin (3 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 604 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-31.
Other skills, from other repositories
implement
Implement a ticket or feature with proportional planning, test first behavior changes, independent review when available, and verification through the real affected surface.
update-architecture-atlas
Create or refresh a versioned Curie architecture-atlas JSON snapshot from a git diff, including current and vision flows, maturity-rated seams, ADRs, and documentation drift. Use when asked to update, regenerate, compare, or add a version to the interactive architecture atlas.
magic-compact
Compact this Claude Code session.
sre-bot
Answer questions about production health and investigate incidents using live Kubernetes and observability data. Invoke whenever someone asks whether something is broken, slow, erroring, or down; asks what happened during an outage or time window; asks about alerts, logs, metrics, traces, or error rates; asks why a…
weather
Look up a location's weather forecast using a live web search. Invoke whenever the user asks about the weather, whether to expect rain, temperature, or what to wear or plan for outdoor activities.
coder
Make focused changes in the managed repository workspace and request platform publication when asked.