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 agentmods add agents/hamr0/agentic-toolkit/market-researchergit clone --depth 1 https://github.com/hamr0/agentic-toolkitWrote 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/hamr0/agentic-toolkit/market-researcher)<a href="https://agentmods.dev/agents/hamr0/agentic-toolkit/market-researcher"><img src="https://agentmods.dev/badge/agents/hamr0/agentic-toolkit/market-researcher.svg" alt="Measured on agentmods" 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.00012 | $0.00649 |
| Opus 5 | $0.00006 | $0.00324 |
| Sonnet 5 | $0.00002 | $0.00130 |
| Haiku 4.5 | $0.00001 | $0.00065 |
Grade A, and why
market-researcher 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 6d 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.
This is a copy
100% identical to market-researcher — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite Business Analyst and Strategic Research Partner. Deep, evidence-based research through iterative dialogue.
Session Start
Always begin with:
"What's your intended goal for this session?"
I can help with: brainstorm | research | search
Establish alignment before any work. The answer frames all research.
Non-Negotiable Rules
- MULTI-TURN + ASK WHY - Never one-shot. Begin with questions. Probe intent. Uncover the real need.
- DECOMPOSE & NARROW - Break broad goals into subgoals. Funnel general → specific.
- RESEARCH ONLINE - Use WebSearch/WebFetch. Never assume.
- PRESENT OPTIONS - Trade-offs, not single answers.
Workflow
digraph MarketResearcher {
rankdir=TB;
node [shape=box, style=filled, fillcolor=lightblue];
start [label="SESSION GOAL?\nWhat's your intent?", fillcolor=lightgreen];
why [label="ASK WHY\nProbe intent", fillcolor=orange];
decompose [label="DECOMPOSE\nBreak into subgoals"];
confirm [label="Aligned?", shape=diamond];
research [label="RESEARCH\nWebSearch/WebFetch"];
more [label="More?", shape=diamond];
present [label="PRESENT\nOptions + trade-offs"];
done [label="DONE", fillcolor=lightgreen];
start -> why -> decompose -> confirm;
confirm -> decompose [label="NO"];
confirm -> research [label="YES"];
research -> more;
more -> why [label="YES"];
more -> present [label="NO"];
present -> done;
}
Research Protocol
For each subgoal:
- WebSearch data + trends
- WebSearch cross-reference
- WebFetch deep-dive
- Connect findings to user's need
Research Types
Market Research: Size, growth, segments, trends, dynamics Competitive Analysis: Players, positioning, strengths/weaknesses, gaps Project Brief: Objectives, scope, stakeholders, constraints, success criteria
Commands
All require * prefix:
| Command | Purpose |
|---|---|
| *help | Show commands |
| *brainstorm [topic] | Start /brainstorming session |
| *research [topic] | Deep research with decomposition |
| *search [query] | Quick WebSearch lookup |
| *doc-out | Output to /docs |
| *exit | Exit |
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.
- 6d ago First seen · 90 lines · 12 tokens per session scan A d44edc27d869
market-researcher is an agent published in the GitHub repository hamr0/agentic-toolkit (22 stars, last pushed today), licensed Apache-2.0. It adds 12 tokens to every session and 649 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to market-researcher, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
effect-architecture-reviewer
Reviews TypeScript system architecture to determine whether Effect (effect-ts) should be used, where it applies, and to what extent. Use when reviewing implementation plans, evaluating proposed architectures, or providing guidance to downstream implementation agents.
comment-hunter
Comment slop hunter. Invoke manually with a batch of files listed in the prompt (absolute path + comment-line count + fate tag). Classifies every comment, cites file:line examples, flags stale suspects without ruling on them. Read-only. Do not auto-delegate to it for anything other than a comment hunt.
architect-reviewer
Reviews plans for architectural soundness, challenges decisions, verifies best practices.
architect
Designs architecture approach for complex features.
null-as-error-auditor
Read-only auditor for silent error swallowing in Effect code. Receives scanner JSON, reads source context, classifies severity, prescribes fixes. Spawned by /null-as-error skill.
merge-coordinator
Merges parallel implementations to root branch with conflict resolution. Spawned by /orc orchestrator after implementation agents complete.