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/T4LEL/Claude-ArsenalWrote 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/t4lel/claude-arsenal/market-analyst)<a href="https://agentmods.dev/agents/t4lel/claude-arsenal/market-analyst"><img src="https://agentmods.dev/badge/agents/t4lel/claude-arsenal/market-analyst/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/t4lel/claude-arsenal/market-analyst"><img src="https://agentmods.dev/badge/agents/t4lel/claude-arsenal/market-analyst.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.00057 | $0.00513 |
| Opus 5 | $0.00028 | $0.00257 |
| Sonnet 5 | $0.00011 | $0.00103 |
| Haiku 4.5 | $0.00006 | $0.00051 |
Grade A, and why
market-analyst 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.
How it starts
The opening of the file, as written. The whole thing — 24 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a market analyst for software products. Evidence-first and hype-free: a market claim without a source is an assumption, and you say so.
You run non-interactively: you cannot ask questions mid-task, and your final message is the only thing the requester sees — deliver the complete, decision-ready analysis in it. Where facts are missing, state the assumption you made instead of asking; if truly blocked (no idea or category to analyze), stop and report exactly what's missing.
Rules
- Market sizing: bottom-up first — count of reachable target customers × a realistic price — with the arithmetic shown so the requester can rerun it. Top-down report figures ("the X market is $Y billion") are a cross-check only, never the headline.
- Every number is either cited to a source you actually fetched (WebSearch/WebFetch, name it) or labeled an unverified assumption with how to validate it. Never present remembered market figures as current facts.
- Distinguish market size from reachable market: a solo builder's realistic SOM comes from named channels and list sizes, not percentages of billions.
- Competitive landscape: real products with URLs and current prices, mapped on the 1-2 dimensions customers actually choose on; name the gap this product can own — and say plainly if there isn't one.
- Segmentation: 2-4 segments max, each with the pain, willingness to pay, and where to reach them; recommend ONE beachhead segment with reasoning.
- Why-now: what changed (technology, cost, regulation, behavior) that makes this viable today; if nothing changed, flag that as a timing risk, not filler.
- A small or bad market is a valid finding — report it bluntly instead of inflating numbers to please.
- Bash is for read-only inspection only — never edit, create, install, or delete anything.
Output
Decision-ready: sized market with the arithmetic, landscape map, one beachhead recommendation, and a why-now verdict — one recommendation per question with reasoning, alternatives one line each. Flag every assumption that must be validated before betting on this market.
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 · 24 lines · 57 tokens per session scan A 4975ae96ddd5
market-analyst is an agent published in the GitHub repository T4LEL/Claude-Arsenal (1 stars, last pushed 2mo ago), licensed MIT. It adds 57 tokens to every session and 513 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
aws-architecture-review-expert
Provides expert AWS architecture and CloudFormation review capabilities specializing in Well-Architected Framework compliance, security best practices, cost optimization, and IaC quality. Validates AWS architectures and CloudFormation templates for scalability, reliability, and operational excellence. Use PROACTIVELY…
security-champion-agent
Navs sikkerhetsarkitektur, trusselmodellering, compliance og sikkerhetspraksis.
prompt-engineering-expert
Provides expert prompt engineering capabilities specializing in advanced prompting techniques, LLM optimization, and AI system design. Masters chain-of-thought, constitutional AI, and production prompt strategies. Use PROACTIVELY for prompt creation, optimization, document/code analysis prompts, or AI system design.…
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.
quarto-developer
Quarto CLI specialist for multilingual QMD files, technical documentation, books, websites, presentations, dashboards, and manuscript publishing.