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 commands/zxpmail/reqforge/domain-mappergit clone --depth 1 https://github.com/zxpmail/ReqForgeWhat 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 | $0.00014 | $0.00344 |
| Opus 5 | $0.00007 | $0.00172 |
| Sonnet 5 | $0.00003 | $0.00069 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
domain-mapper 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 2d 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
Command: /domain-mapper
Entry: /domain-mapper <domain> or describe what you want to research. Full workflow → SKILL.md.
Quick start
| Step | Action |
|---|---|
| 1 | Define scope — what domain, how deep (L1 snapshot / L2 standard / L3 deep) |
| 2 | Domain snapshot → domain-map.md (brands, products, customers, biz model, pain points, social channels, keywords) |
| 3 | (L2/L3) Deep-dive per competitor/entity → competitor-analysis.md |
| 4 | (L3) Social/media analysis → social-analysis.md |
| 5 | (L3) Synthesis → domain-map.md updated with contradictions, roadmap, risks, blind spots |
Depth levels
| Level | Outputs | Time |
|---|---|---|
| L1 Snapshot | domain-map.md |
~30 min |
| L2 Standard | domain-map.md + competitor-analysis.md |
~1-2 h |
| L3 Deep | domain-map.md + competitor-analysis.md + social-analysis.md |
~half day |
Notes
- Each step pauses for user direction — not a fire-and-forget pipeline
- Every claim is source-attributed in the output
- Timestamped: re-run if >30 days old
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.
- 2d ago First seen · 33 lines · 14 tokens per session scan A e144d7fc0e6b
domain-mapper is a command published in the GitHub repository zxpmail/ReqForge (18 stars, last pushed 12d ago), licensed MIT. It adds 14 tokens to every session and 344 once invoked, about $0.0001 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-30.
Other commands, from other repositories
constitution
根据交互输入或已提供原则创建或更新项目章程，并确保相关模板保持同步。.
meta-theory-verify
Run the appropriate MetaKim verification path.
cross-research
Two-phase multi-model research. Phase A fans codex+gemini in parallel (benchmarks + citations angles); Phase B synthesises via fresh Claude session. Usage: /cross-research [--with | list | compare].
ijfw-audit
Run the IJFW audit gate for the current workflow phase. Usage: /ijfw-audit [phase name].
memory-why
Show why a memory recall returned what it did -- BM25 vs vector vs hybrid provenance.
ijfw-execute
Jump directly to the IJFW workflow Execute phase (Deep D4 / Quick Q3). Usage: /ijfw-execute [task or phase name].