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/market-signal-radar)<a href="https://agentmods.dev/agents/daddia/claude-for-strategy/market-signal-radar"><img src="https://agentmods.dev/badge/agents/daddia/claude-for-strategy/market-signal-radar/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/market-signal-radar"><img src="https://agentmods.dev/badge/agents/daddia/claude-for-strategy/market-signal-radar.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.00043 | $0.00254 |
| Opus 5.5 | $0.00017 | $0.00102 |
| Sonnet 5.5 | $0.00009 | $0.00051 |
| Haiku 4.5 | $0.00004 | $0.00025 |
Grade A, and why
market-signal-radar 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 1mo 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
Market Signal Radar
Runs weekly by default — override to match the cadence in the practice profile.
What it does
-
Reads the practice profile for market definition, signal taxonomy, and materiality thresholds for non-competitor signals (regulation, macro, category shifts, supplier moves).
-
Searches for recent activity matching those signal types. Works with native web search; optional
~~web monitoringMCP improves coverage. -
Classifies each signal by type, geography, and whether it would change the stated market definition or strategic-group boundaries.
-
Surfaces only map- or plan-changing signals via
~~chat— routine noise is dropped.
Fallback with no ~~chat connected
Compiles the same digest inline for the market-intelligence lead to distribute manually.
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.
- 1mo ago First seen · 28 lines · 43 tokens per session scan A 2271fda8fcba
market-signal-radar is an agent published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 254 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
parity-auditor
Audit code migrations for missing functionality. Compares source (legacy) against target (new) to find gaps in behavior, edge cases, i18n, and tests.
test-auditor
Audit test effectiveness beyond coverage. Invoke when writing tests or before PRs.
security-auditor
Read-only security audit of a diff or module — exploitable flaws at trust boundaries. Invoke from review, or for a security pass before merge.
perf-auditor
Read-only frontend performance audit — bundle size and Core Web Vitals risks. Invoke from review, or for a performance pass on a web app.
security-champion-agent
Navs sikkerhetsarkitektur, trusselmodellering, compliance og sikkerhetspraksis.
accessibility-agent
WCAG 2.1/2.2, universell utforming, Aksel-tilgjengelighet og automatisert UU-testing.