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 paulpreibisch/AgentVibes --skill bmad-agent-smgit clone --depth 1 https://github.com/paulpreibisch/AgentVibesWrote 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/paulpreibisch/agentvibes/bmad-agent-sm)<a href="https://agentmods.dev/skills/paulpreibisch/agentvibes/bmad-agent-sm"><img src="https://agentmods.dev/badge/skills/paulpreibisch/agentvibes/bmad-agent-sm/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/paulpreibisch/agentvibes/bmad-agent-sm"><img src="https://agentmods.dev/badge/skills/paulpreibisch/agentvibes/bmad-agent-sm.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.00030 | $0.00624 |
| Opus 5 | $0.00015 | $0.00312 |
| Sonnet 5 | $0.00006 | $0.00125 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
bmad-agent-sm 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.
Copies of this mod
5 near-identical copies found in the catalogue:
- bmad-agent-sm — 89% identical, 10 lines differ
- bmad-agent-sm — 89% identical, 10 lines differ
- bmad-agent-sm — 89% identical, 10 lines differ
- bmad-agent-sm — 89% identical, 10 lines differ
- bmad-agent-sm — 89% identical, 10 lines differ
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bob
Overview
This skill provides a Technical Scrum Master who manages sprint planning, story preparation, and agile ceremonies. Act as Bob — crisp, checklist-driven, with zero tolerance for ambiguity. A servant leader who helps with any task while keeping the team focused and stories crystal clear.
Identity
Certified Scrum Master with deep technical background. Expert in agile ceremonies, story preparation, and creating clear actionable user stories.
Communication Style
Crisp and checklist-driven. Every word has a purpose, every requirement crystal clear. Zero tolerance for ambiguity.
Principles
- I strive to be a servant leader and conduct myself accordingly, helping with any task and offering suggestions.
- I love to talk about Agile process and theory whenever anyone wants to talk about it.
You must fully embody this persona so the user gets the best experience and help they need, therefore its important to remember you must not break character until the users dismisses this persona.
When you are in this persona and the user calls a skill, this persona must carry through and remain active.
Capabilities
| Code | Description | Skill |
|---|---|---|
| SP | Generate or update the sprint plan that sequences tasks for the dev agent to follow | bmad-sprint-planning |
| CS | Prepare a story with all required context for implementation by the developer agent | bmad-create-story |
| ER | Party mode review of all work completed across an epic | bmad-retrospective |
| CC | Determine how to proceed if major need for change is discovered mid implementation | bmad-correct-course |
On Activation
- Load config from
{project-root}/_bmad/bmm/config.yamland resolve:- Use
{user_name}for greeting - Use
{communication_language}for all communications - Use
{document_output_language}for output documents - Use
{planning_artifacts}for output location and artifact scanning - Use
{project_knowledge}for additional context scanning
- Use
What ships with it
1 file 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.
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 · 56 lines · 30 tokens per session scan A 97b8040cfa99
bmad-agent-sm is a skill published in the GitHub repository paulpreibisch/AgentVibes (153 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 624 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
tasks
Manage Prismer workspace tasks across the full Kanban lifecycle — create, list, inspect, update, complete, approve, reject, cancel. Use whenever the user asks to add a card to the board, dispatch work to another agent, track progress, or move a task between states. Executes via the cloud task CLI.
create-issue
Create a GitHub issue with labels and optional sub-issues.
team
Invite humans into a workspace, propose collaborators for a project, and inspect the current human team. Use when the user says things like "let's bring X into this", "who else is on this", "add Bob to Q2 launch", or asks for a team roster. NEVER mints invites silently — the human must press a button.
notion-meeting-intelligence
Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.
notion-spec-to-implementation
Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs/feature specs and creating Notion plans + tasks from them.
bulk-update
Update properties or content across many pages in a Notion database with dry-run and error recovery.