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.
git clone --depth 1 https://github.com/daddia/claude-for-strategyWrote 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/agents/daddia/claude-for-strategy/competitive-signal-scan)<a href="https://agentmods.dev/agents/daddia/claude-for-strategy/competitive-signal-scan"><img src="https://agentmods.dev/badge/agents/daddia/claude-for-strategy/competitive-signal-scan/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/agents/daddia/claude-for-strategy/competitive-signal-scan"><img src="https://agentmods.dev/badge/agents/daddia/claude-for-strategy/competitive-signal-scan.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.00052 | $0.00383 |
| Opus 5 | $0.00026 | $0.00192 |
| Sonnet 5 | $0.00010 | $0.00077 |
| Haiku 4.5 | $0.00005 | $0.00038 |
Grade A, and why
competitive-signal-scan 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 10d 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
Competitive Signal Scan
Runs weekly by default — override to match the cadence in the practice profile.
What it does
-
Reads the practice profile for the named competitor set and what specifically counts as a meaningful signal (pricing changes, executive departures, funding rounds, product launches, etc. — whatever was recorded during setup).
-
Searches for recent activity matching those signal types for each named competitor. This is the one agent in the repo that can do meaningful work using this environment's native web search, with no MCP connector required — a dedicated news/monitoring connector (see
CONNECTORS.md) improves reliability and breadth for serious ongoing use, but isn't a blocker to getting value immediately. -
For anything found, checks relevance against the existing strategic-group map and incentive map (if either has been built): does this signal suggest a competitor is moving across a mobility barrier identified earlier, or does it reveal something about a competitor's incentive structure that updates a prior
map-incentivesprediction? -
Surfaces only what's actually new or map-changing via
~~chat— explicitly avoid reporting routine, expected activity that doesn't update anything; a weekly digest of things that don't matter trains people to ignore it.
Fallback with no ~~chat connected
Without a chat connector, compiles the same findings and surfaces them directly in conversation rather than pushing externally.
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.
- 10d ago First seen · 29 lines · 52 tokens per session scan A c6870cacb24f
competitive-signal-scan is an agent published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 383 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 agents, from other repositories
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms. Use PROACTIVELY for data pipeline design, analytics infrastructure, or modern data stack implementation.
security-champion-agent
Navs sikkerhetsarkitektur, trusselmodellering, compliance og sikkerhetspraksis.
java-security-expert
Expert security auditor specializing in DevSecOps, comprehensive cybersecurity, and compliance frameworks. Masters vulnerability assessment, threat modeling, secure authentication (OAuth2/OIDC), OWASP standards, cloud security, and security automation. Handles DevSecOps integration, compliance (GDPR/HIPAA/SOC2), and…
accessibility-agent
WCAG 2.1/2.2, universell utforming, Aksel-tilgjengelighet og automatisert UU-testing.
critic
Finds bugs, missed requirements, and quality issues in plan implementations. Spawned after all tasks pass review for a final sweep.