What is bmad-technical-research?

A retired technical-research command that passes requests to bmad-deep-recon, a newer tool for preparing and processing research across technical and other subjects.

Use it when an existing workflow still calls bmad-technical-research. New technical research should use bmad-deep-recon instead.

It preserves older workflows while moving research work to the consolidated tool.

How 2233admin/design-pipeline configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to 2233admin/design-pipeline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/2233admin/design-pipeline/main/.agents/skills/bmad-technical-research/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/2233admin/design-pipeline

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/2233admin/design-pipeline/bmad-technical-research/github.svg)](https://agentmods.dev/skills/2233admin/design-pipeline/bmad-technical-research)

Your own site

<a href="https://agentmods.dev/skills/2233admin/design-pipeline/bmad-technical-research"><img src="https://agentmods.dev/badge/skills/2233admin/design-pipeline/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/2233admin/design-pipeline/bmad-technical-research"><img src="https://agentmods.dev/badge/skills/2233admin/design-pipeline/bmad-technical-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 432 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00021	$0.00432
Opus 5	$0.00010	$0.00216
Sonnet 5	$0.00004	$0.00086
Haiku 4.5	$0.00002	$0.00043

Measured 9d ago against content hash d8e6177fc03c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

bmad-technical-research — 100% identical, 0 lines differ

.agents/skills/bmad-technical-research/SKILL.md · 15 lines

What it actually says

DEPRECATED — forwards to bmad-deep-recon (technical type)

This skill was consolidated into bmad-deep-recon. It is retained as a thin compatibility shim so existing invocations by name and _bmad/custom/bmad-technical-research.toml override files keep working. New work should invoke bmad-deep-recon directly — it drafts deep-research prompts for outside tools, processes finished reports into downstream-ready summaries, and runs research directly, across market, domain, technical, competitive, user-voice, and academic-lit types (plus a select shape for choose-between decisions and custom types).

On Activation

Resolve customization: uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow. This picks up any {project-root}/_bmad/custom/bmad-technical-research.toml and bmad-technical-research.user.toml overrides for the legacy fields (activation_steps_prepend, activation_steps_append, persistent_facts, on_complete).
Emit a deprecation notice to the user (in their configured communication language): bmad-technical-research is deprecated and forwards to bmad-deep-recon with the technical type. To silence this notice and access the full new surface (draft/process/run modes, research types, verification levels, HTML briefing, handoffs), migrate _bmad/custom/bmad-technical-research.toml to _bmad/custom/bmad-deep-recon.toml and invoke bmad-deep-recon directly.
Invoke bmad-deep-recon with: research type technical (skip its type inference), the four legacy fields above as pre-resolved values, and the user's original input verbatim. bmad-deep-recon takes the workflow from here — do not execute any further steps in this shim.

Changes

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 · 15 lines · 21 tokens per session scan A d8e6177fc03c

Subscribe to this mod's changes

bmad-technical-research is a skill published in the GitHub repository 2233admin/design-pipeline (9 stars, last pushed 5d ago), licensed MIT. It adds 21 tokens to every session and 432 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.

Claude Code Research ai-agents codex-cli design-system design-tokens frontend-development

omd-apply

A skill that applies a project's DESIGN.md file as visual and brand guidance for interface work. It covers components, colors, fonts, layout, copy, motion, and visual assets.

kwakseongjae/oh-my-design · 129 tokens

ss-review

Review UI code for design system compliance, accessibility, and best practices.

bitjaru/styleseed · 16 tokens

ss-pattern

Generate a composed UI pattern from the active StyleSeed grammar and brand recipe using existing primitives.

bitjaru/styleseed · 21 tokens

ss-restyle

Apply one optional StyleSeed aesthetic profile without changing the selected output grammar, product job, or core design judgment.

bitjaru/styleseed · 26 tokens

design-system-tokens

Design token management with the W3C Design Token spec, three-tier hierarchy (global/alias/component), OKLCH color, Style Dictionary transforms, and dark mode theming. Use when creating token files, implementing theme systems, or building design-to-code pipelines.

yonatangross/orchestkit · 58 tokens

governance-encoder

Convert governance policies into machine-executable JSON constraint files that AI agents and CI pipelines validate against automatically. This produces rule engine files in .ai/governance/, NOT narrative decision records or documentation. Trigger when someone says: encode governance rules, governance as code, automate…

murphytrueman/design-system-ops · 116 tokens

design-pipeline: Skill for Claude Code