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/bma-d/bmad-story-automatorWrote 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/plugins/bma-d/bmad-story-automator/marketplace)<a href="https://agentmods.dev/plugins/bma-d/bmad-story-automator/marketplace"><img src="https://agentmods.dev/badge/plugins/bma-d/bmad-story-automator/marketplace/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/plugins/bma-d/bmad-story-automator/marketplace"><img src="https://agentmods.dev/badge/plugins/bma-d/bmad-story-automator/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
bmad-plugins marketplace 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 10d 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
{
"name": "bmad-plugins",
"description": "BMAD Claude Code plugins for story automation and workflow orchestration.",
"owner": {
"name": "bma-d",
"email": "[email protected]"
},
"plugins": [
{
"name": "bmad-automator",
"source": {
"source": "github",
"repo": "bmad-code-org/bmad-automator"
},
"description": "BMAD story automation skills for create/dev/QA/review/retro orchestration.",
"author": {
"name": "bma-d",
"email": "[email protected]"
},
"homepage": "https://github.com/bmad-code-org/bmad-automator#readme",
"repository": "https://github.com/bmad-code-org/bmad-automator",
"license": "MIT",
"keywords": [
"bmad",
"story-automation",
"claude-code",
"skills",
"workflow"
],
"category": "Workflow Automation",
"tags": [
"bmad",
"automation",
"story-workflow"
]
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json 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.
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.
- 10d ago First seen · 39 lines scan A af0c159936a3
bmad-plugins marketplace is a plugin published in the GitHub repository bma-d/bmad-story-automator (2 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
before-you-build
Pre-build product risk review for founders, product teams, and AI-assisted builders before implementation starts.
obw
Obsidian Workspace — project-scoped vault productivity (capture / notes / PM). Skills-only: owns folder layout and templates; runs the Obsidian CLI directly via the official obsidian-cli skill.
mission-control
SDLC management for Operations, Asgard, and CAMPPS: prepared issue drafts, live schema sync, board schemas, labels, project fields, metrics, and card validation.
feishu-calendar
Manage Feishu (Lark) calendar events — create, read, update, delete events and manage attendees via the Feishu Open Platform Calendar API v4.
gse
GSE-One — AI engineering companion for structured SDLC management. 24 commands, adaptive risk analysis, unified backlog, knowledge transfer, worktree isolation.
product-management
Write feature specs, plan roadmaps, and synthesize user research faster. Keep stakeholders updated and stay ahead of the competitive landscape.