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/wonsukchoi/domain-expertsWrote 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/wonsukchoi/domain-experts/scan-project)<a href="https://agentmods.dev/commands/wonsukchoi/domain-experts/scan-project"><img src="https://agentmods.dev/badge/commands/wonsukchoi/domain-experts/scan-project.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.00022 | $0.00312 |
| Opus 5 | $0.00011 | $0.00156 |
| Sonnet 5 | $0.00004 | $0.00062 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
scan-project 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 7d 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
Target project: "$ARGUMENTS"
Tell the user up front, in one line, that this reads local project files (stack, README, directory structure, recent commit messages) to propose suggestions, and nothing about the project itself is written anywhere or leaves this conversation.
- Run the
scan-projectworkflow (.claude/workflows/scan-project.js) via the Workflow tool, withargs: {projectPath: "$ARGUMENTS"}. - Present the returned
suggestionsvia AskUserQuestion as a multi-select: each option's label is theneed, description shows therationaleandconfidence, and any suggestion withcli_confident: truemust say so explicitly (e.g. "already likely covered by<cli_best_slug>") since picking it will probably resolve touse_existingrather than draft something new. - For every need the user selects, run the
generate-roleworkflow (.claude/workflows/generate-role.js, unmodified) with that exact need text asargs, one at a time — not in parallel, so PR branches/commits don't race each other. - Report each result (use_existing / abandoned / shipped + PR link) as it completes. If the user selects nothing, say so and stop — no files change.
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.
- 7d ago First seen · 14 lines · 22 tokens per session scan A 5605385c64c0
scan-project is a command published in the GitHub repository wonsukchoi/domain-experts (15 stars, last pushed 7d ago), licensed MIT. It adds 22 tokens to every session and 312 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
prisma-optimize
Optimize Prisma queries with automated analysis, N+1 detection, index recommendations, and performance patterns based on official documentation.
design-mobile
Design a mobile screen or flow. This command never writes SwiftUI or Compose — the deliverable is a device-framed HTML mockup plus a handoff spec for the platform developer.
run-tasks
Execute GitHub issues using full EPCT workflow (Explore-Plan-Code-Test). Converts issue requirements into completed PR.
design-page
Routes a new page or screen in an existing project by register and move; taste-first may defer existing tokens until concept lock.
test
Test commit. Use for add tests, update tests, test coverage, unit test, spec.
checklist
Generate a custom checklist for the current feature based on user requirements.