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/ddhjx-code/demand-discovery-skill/demand-discoverygit clone --depth 1 https://github.com/Ddhjx-code/Demand-Discovery-SkillWrote 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/commands/ddhjx-code/demand-discovery-skill/demand-discovery)<a href="https://agentmods.dev/commands/ddhjx-code/demand-discovery-skill/demand-discovery"><img src="https://agentmods.dev/badge/commands/ddhjx-code/demand-discovery-skill/demand-discovery.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 | $0.00015 | $0.00180 |
| Opus 5 | $0.00008 | $0.00090 |
| Sonnet 5 | $0.00003 | $0.00036 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
demand-discovery 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 3d 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
You are running the demand-discovery workflow.
Category to research (if specified): "$ARGUMENTS"
Instructions:
- Read file: SKILL.md — this contains the complete 9-stage workflow
- Read file: references/niche-rotation.md — 26 categories with keywords
- Read file: references/estimation-methodology.md — scoring formulas
If no category is specified, read output/tracker.md (relative to skill directory) to find the next unresearched category in the rotation.
Follow the workflow in SKILL.md exactly. Use MCP tools if available, otherwise use shell commands (uvx niche-*-mcp) or web search to gather data.
Output the report to output/reports/YYYY-MM-DD-.md (relative to skill directory)
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.
- 3d ago First seen · 19 lines · 15 tokens per session scan A 57f84eed5be5
demand-discovery is a command published in the GitHub repository Ddhjx-code/Demand-Discovery-Skill (1 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 180 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-31.
Other commands, from other repositories
constitution
根据交互输入或已提供原则创建或更新项目章程，并确保相关模板保持同步。.
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].
ijfw-metrics
Show IJFW token / cost / session metrics over a time window. Reads .ijfw/metrics/sessions.jsonl via the ijfwmetrics MCP tool.