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 b2bforce/b2bforce --skill intel-competitor-monitoringgit clone --depth 1 https://github.com/b2bforce/b2bforceWrote 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/b2bforce/b2bforce/intel-competitor-monitoring)<a href="https://agentmods.dev/skills/b2bforce/b2bforce/intel-competitor-monitoring"><img src="https://agentmods.dev/badge/skills/b2bforce/b2bforce/intel-competitor-monitoring/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/b2bforce/b2bforce/intel-competitor-monitoring"><img src="https://agentmods.dev/badge/skills/b2bforce/b2bforce/intel-competitor-monitoring.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.00060 | $0.01839 |
| Opus 5 | $0.00030 | $0.00920 |
| Sonnet 5 | $0.00012 | $0.00368 |
| Haiku 4.5 | $0.00006 | $0.00184 |
Grade A, and why
intel-competitor-monitoring 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitor Monitoring
Files-only workflow for monitoring external companies/competitors in a shared
repo. The source of truth is committed Markdown under workspace/.
There is no hidden runtime state. This makes the workflow easier to review, merge, and hand to another agent or teammate.
Read Firm Context First
Before adding or crawling competitors:
- Read
workspace/firm/profile.mdfor firm scope, services, geography, and known competitors. - Read existing competitor folders under
workspace/intelligence/competitors/{slug}/. - Write findings and weekly exports to
workspace/intelligence/reports/.
When to Use
- User asks for competitor monitoring, account tracking, or website change detection.
- A competitor profile exists and pages should be crawled or refreshed.
- Discovery produced candidate competitors and the user confirmed which ones to monitor.
- Weekly report needs change artifacts to summarize.
Core Rules
Brand scope. Competitors stay shared in a multi-brand workspace — one profile per company, however many brands it competes with. !_profile.md declares brands: [...] and the "why it matters" section says why per brand. See the Brand Scope Gate in AGENTS.md.
- One competitor = one folder:
workspace/intelligence/competitors/{slug}/. - Homepage is monitored by default when a competitor is added.
- Discovered subpages default to
monitor: false; the user must approve them before recurring crawls. - First crawl stores a baseline snapshot only. It must not create a business change alert.
- Every later crawl compares against the latest previous snapshot for the same page slug.
- Significant changes are written as Markdown change artifacts; minor/noisy
changes may be omitted or marked
significance: minor. - Never invent changes. If scraping fails or content is incomplete, write a
crawl note with
status: errorinstead of summarizing guessed differences.
File Layout
Use the structure documented in references/file-layout.md:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 264 lines · 60 tokens per session scan A b2693c96eb66
intel-competitor-monitoring is a skill published in the GitHub repository b2bforce/b2bforce (2 stars, last pushed 20d ago), licensed MIT. It adds 60 tokens to every session and 1,839 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-31.
Other skills, from other repositories
competitor-monitoring
Use this skill when you need to know what rival companies are doing — "what are my competitors doing", "competitor update", "competitor news", "competitive landscape", "market intel", "what's new with [company]", "track [company]", "competitor briefing", "who's making moves", "we keep losing deals to [company]" — or…
campaign-analytics
Analyze campaign performance from deliverability through revenue: delivery, engagement, replies, meetings, SQOs, pipeline, CAC, and payback. Produces diagnostic scorecard, root-cause analysis, benchmark comparison, and next-action plan. Use when deciding whether to scale, fix, or kill campaigns.
gtm-metrics
Build a GTM metrics system for SaaS: funnel conversion, pipeline velocity, win rates, CAC, payback, NRR, sales efficiency, growth accounting, and executive dashboards. Use when creating metrics dashboards, board reports, revenue reviews, operating cadence, or diagnosing growth constraints.
event-room-intelligence
Use this skill 1 to 3 days before any face-to-face event where you hold a registration export (a talk, conference, dinner, booth) and the question is 'I have the attendee CSV, who should I talk to?'. It maps every registrant to a company, joins the list against the live CRM, LinkedIn-verifies every person's title and…
a-b-testing
Design statistically sound GTM experiments for copy, channels, landing pages, sequencing, pricing, and funnel conversion. Produces hypothesis, sample-size logic, success metrics, test plan, analysis method, and scale/stop/kill recommendation. Use when planning A/B tests, split tests, or experiment roadmaps.
attribution
Build practical B2B attribution models across first touch, lead creation, opportunity creation, multi-touch, account-based influence, and sales-sourced revenue. Produces model comparison, UTM governance, source-of-truth rules, and channel ROI view. Use when marketing and sales disagree on source or ROI.