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 skills add LarsCowe/bmalph --skill bmad-technical-researchgit clone --depth 1 https://github.com/LarsCowe/bmalphWrote 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/larscowe/bmalph/bmad-technical-research)<a href="https://agentmods.dev/skills/larscowe/bmalph/bmad-technical-research"><img src="https://agentmods.dev/badge/skills/larscowe/bmalph/bmad-technical-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/larscowe/bmalph/bmad-technical-research"><img src="https://agentmods.dev/badge/skills/larscowe/bmalph/bmad-technical-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00031 | $0.00047 |
| Opus 5 | $0.00015 | $0.00023 |
| Sonnet 5 | $0.00006 | $0.00009 |
| Haiku 4.5 | $0.00003 | $0.00005 |
Grade A, and why
bmad-technical-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.
What it actually says
Follow the instructions in ./workflow.md.
What ships with it
9 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.
- bmad-skill-manifest.yaml 12 B
- research.template.md 581 B
- technical-steps/step-01-init.md 5.5 KB
- technical-steps/step-02-technical-overview.md 9.2 KB
- technical-steps/step-03-integration-patterns.md 9.8 KB
- technical-steps/step-04-architectural-patterns.md 7.0 KB
- technical-steps/step-05-implementation-research.md 7.6 KB
- technical-steps/step-06-research-synthesis.md 21 KB
- workflow.md 2.3 KB
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 · 7 lines · 31 tokens per session scan A 1f3d94b202b3
bmad-technical-research is a skill published in the GitHub repository LarsCowe/bmalph (406 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 47 once invoked, about $0.0002 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 skills, from other repositories
github-operations
GitHub CLI operations for issues, PRs, milestones, and Projects v2. Covers gh commands, REST API patterns, and automation scripts. Use when managing GitHub issues, PRs, milestones, or Projects with gh.
joycraft-new-feature
Guided feature development — interview the user, produce a Feature Brief, then decompose into atomic specs.
joycraft-decide
Invoked at the design bookend by decompose's decision gate or the human directly — turn open questions into a decision dossier; every decision terminates clarified, backlogged, discarded, or assigned.
joycraft-tune
Assess and upgrade your project's AI development harness — score 7 dimensions, apply fixes, show a harness maturity roadmap.
joycraft-session-end
Wrap up a session — capture discoveries, verify, prepare for PR or next session.
joycraft-add-fact
Invoked by session-end or the human after a fact surfaces — route it to the correct context document (production map, dangerous assumptions, decision log, institutional knowledge, troubleshooting).