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 indranilbanerjee/digital-marketing-pro --skill competitor-alertsgit clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-proWrote 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/indranilbanerjee/digital-marketing-pro/competitor-alerts)<a href="https://agentmods.dev/skills/indranilbanerjee/digital-marketing-pro/competitor-alerts"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/competitor-alerts/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/indranilbanerjee/digital-marketing-pro/competitor-alerts"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/competitor-alerts.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.00026 | $0.03055 |
| Opus 5.5 | $0.00010 | $0.01222 |
| Sonnet 5.5 | $0.00005 | $0.00611 |
| Haiku 4.5 | $0.00003 | $0.00305 |
Grade A, and why
competitor-alerts 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- competitor-alerts — 95% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/digital-marketing-pro:competitor-alerts
Purpose
Configure an intelligent competitor alert system that surfaces competitive changes worth knowing about while actively managing alert fatigue. Define what types of competitive changes should trigger notifications, at what significance thresholds, for which competitors, through which channels, and at what urgency tier. Competitive monitoring generates a high volume of raw change signals — most are noise that does not warrant human attention. This command transforms raw change detection into actionable competitive intelligence by applying tiered urgency rules, smart thresholds calibrated to each dimension's natural volatility, and digest batching that groups lower-priority changes into periodic summaries rather than individual pings. The result is a competitor alert pipeline that reliably surfaces high-impact competitive moves in real-time while packaging routine competitive activity into digestible periodic briefings that maintain awareness without disruption. Supports per-competitor and per-dimension alert customization so the user can watch a primary rival more closely with tighter thresholds while applying lighter monitoring to secondary and emerging competitors.
Input Required
The user must provide (or will be prompted for):
- Competitors to monitor: Which tracked competitors should have alerts enabled — can be all currently monitored competitors from competitor-monitor or a specific subset. Each competitor can have fully independent alert configurations, allowing tighter trigger thresholds and higher default urgency for primary rivals versus secondary competitors. Competitors must have existing baselines from competitor-monitor to enable meaningful change detection; if any requested competitors lack baselines, the user is prompted to run competitor-monitor first to establish the reference state
- Alert types to enable: Which competitive change categories to monitor —
content(new pages published, significant edits to key pages, messaging or value proposition changes),pricing(any pricing page change, plan restructuring, new discount offers or promotions, free trial modifications),ads(new campaign launches in Google Ads or Meta, major creative rotations, new advertising platform presence),social(mention volume spikes, sentiment shifts, viral content, significant follower growth),ranking(organic position changes on tracked keywords beyond the configured threshold),serp(featured snippet ownership changes, People Also Ask presence shifts, knowledge panel updates, AI overview citation changes),positioning(correlated changes across multiple dimensions suggesting a deliberate strategic shift). Select all for comprehensive alerting or choose specific types per competitor based on competitive priorities - Urgency tiers per alert type: Assignment of each enabled alert type to an urgency tier —
critical(immediate real-time notification for high-impact competitive moves demanding fast response),warning(batched into daily digest for notable but non-urgent changes requiring awareness), orinfo(collected into weekly digest for background intelligence and pattern recognition). If not specified by the user, defaults are applied based on typical competitive impact patterns and dimension sensitivity - Notification channel: Where to deliver alerts — Slack channel name (e.g., #competitor-alerts, #marketing-intel, #urgent-competitive) or email address. Supports specifying different channels per urgency tier for intelligent routing — e.g., critical alerts to #urgent-alerts with @channel mention for immediate visibility, warning alerts to #competitor-daily for morning review, and info alerts bundled into the #competitor-weekly digest. For Slack delivery, requires the Slack MCP server to be connected with posting permissions on the target channels
- Alert mode: Delivery timing preference per urgency tier —
real-time(alerts sent immediately upon change detection, best suited for critical-tier alerts only),daily-digest(all alerts of the tier batched and delivered once per day at a specified time, typically morning), orweekly-digest(all alerts batched into a comprehensive weekly competitive intelligence briefing). Recommended configuration mixes modes by tier — critical alerts in real-time for immediate competitive response, warning alerts in daily digest for daily planning context, info alerts in weekly digest for strategic awareness - Custom thresholds (optional): Override the default change significance thresholds per alert type to tune sensitivity — e.g., "alert on ranking changes greater than 3 positions instead of the default 5", "trigger social alerts at 1.5x baseline mention volume instead of 2x", "alert on any content change to competitor homepages and pricing pages, not just significant edits", "lower ad alert threshold to include creative refreshes not just new campaigns". Allows fine-tuning based on competitive intensity, industry pace, and the user's tolerance for alert volume versus comprehensiveness
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.
- 4d ago Changed · -112 tokens per session 863ea1a91e2a
- 1mo ago First seen · 47 lines · 138 tokens per session scan A 07be7fe93402
competitor-alerts is a skill published in the GitHub repository indranilbanerjee/digital-marketing-pro (882 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 3,055 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-07.
Other skills, from other repositories
cf-brief
Write a research-backed content brief from a keyword or topic: intent, competitors, outline. "brief me on this topic".
cf-publish
Publish a reviewed piece to Webflow or WordPress as draft, scheduled or live. "push this live to WordPress".
cf-template
Create a custom content-type template: sections, word counts, citation minimums. "make a template for our case studies".
cf-variants
Generate scored A/B variants of a headline, opening line, hook or CTA, with a test plan. "give me headline options to test".
cf-translate
Translate a finished piece into 15 languages, keeping brand voice and citations; literal, adapted or transcreated. "translate this into Spanish".
cf-video-script
Write a timestamped video script with B-roll and on-screen text for YouTube, Shorts or Reels. "turn this into a video script".