Borrowing it
Nothing to install: this file belongs to jeffrey2423/commit-like-pro. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jeffrey2423/commit-like-pro/main/.claude/skills/bmad-domain-research/SKILL.mdgit clone --depth 1 https://github.com/jeffrey2423/commit-like-proWrote 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/skills/jeffrey2423/commit-like-pro/bmad-domain-research)<a href="https://agentmods.dev/skills/jeffrey2423/commit-like-pro/bmad-domain-research"><img src="https://agentmods.dev/badge/skills/jeffrey2423/commit-like-pro/bmad-domain-research/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/skills/jeffrey2423/commit-like-pro/bmad-domain-research"><img src="https://agentmods.dev/badge/skills/jeffrey2423/commit-like-pro/bmad-domain-research.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.00027 | $0.01065 |
| Opus 5 | $0.00014 | $0.00532 |
| Sonnet 5 | $0.00005 | $0.00213 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade A, and why
bmad-domain-research 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 9d 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
89% identical to bmad-domain-research — 2 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain Research Workflow
Goal: Conduct comprehensive domain/industry research using current web data and verified sources to produce complete research documents with compelling narratives and proper citations.
Your Role: You are a domain research facilitator working with an expert partner. This is a collaboration where you bring research methodology and web search capabilities, while your partner brings domain knowledge and research direction.
Conventions
- Bare paths (e.g.
domain-steps/step-01-init.md) resolve from the skill root. {skill-root}resolves to this skill's installed directory (wherecustomize.tomllives).{project-root}-prefixed paths resolve from the project working directory.{skill-name}resolves to the skill directory's basename.
PREREQUISITE
⛔ Web search required. If unavailable, abort and tell the user.
On Activation
Step 1: Resolve the Workflow Block
Run: python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow
If the script fails, resolve the workflow block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:
{skill-root}/customize.toml— defaults{project-root}/_bmad/custom/{skill-name}.toml— team overrides{project-root}/_bmad/custom/{skill-name}.user.toml— personal overrides
Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by code or id replace matching entries and append new entries, and all other arrays append.
Step 2: Execute Prepend Steps
Execute each entry in {workflow.activation_steps_prepend} in order before proceeding.
Step 3: Load Persistent Facts
Treat every entry in {workflow.persistent_facts} as foundational context you carry for the rest of the workflow run. Entries prefixed file: are paths or globs under {project-root} — load the referenced contents as facts. All other entries are facts verbatim.
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- customize.toml 1.6 KB
- domain-steps/step-01-init.md 5.3 KB
- domain-steps/step-02-domain-analysis.md 8.4 KB
- domain-steps/step-03-competitive-landscape.md 9.3 KB
- domain-steps/step-04-regulatory-focus.md 6.8 KB
- domain-steps/step-05-technical-trends.md 7.3 KB
- domain-steps/step-06-research-synthesis.md 17 KB
- research.template.md 581 B
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.
- 9d ago First seen · 97 lines · 27 tokens per session scan A 2308f7e21f78
bmad-domain-research is a skill published in the GitHub repository jeffrey2423/commit-like-pro (2 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 1,065 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to bmad-domain-research, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
wttr-weather
Weather via wttr.in GET (no key). Use for weather/forecast; prefer os.http.request.
agent-desktop
Use the built-in Computer sub-agent with agent-desktop for macOS desktop automation. Apply when a task needs application launching, accessibility snapshots, stable element refs, window focusing, semantic clicks/typing, or visual confirmation outside the browser sandbox.
jk
Manage Jenkins controllers with jk, including jobs, runs, logs, artifacts, credentials, nodes, queues, and plugins.
push
Operate a Push personal assistant, inspect its health and jobs, and author or validate Push job runbooks. Use when a request concerns Push setup, CLI commands, assistant files, scheduled jobs, or delivery behavior.
hatch3r-board-refresh
Regenerates the living board overview dashboard from current board state. Scans all open issues, computes health metrics, and updates the meta:board-overview issue.
hatch3r-qa-path
Produces a human-run manual QA test path from a PR, branch diff, or uncommitted working tree — a risk-ordered table of steps, expected results, and automated-coverage references plus a shippability sign-off. Rows are auto-proven via delegated verification sub-agents before emission, so the human walks only what…