Borrowing it
Nothing to install: this file belongs to skyf0xx/hedgehog. 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/skyf0xx/hedgehog/master/.claude/skills/bmad-revendor/SKILL.mdgit clone --depth 1 https://github.com/skyf0xx/hedgehogWrote 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/skyf0xx/hedgehog/bmad-revendor)<a href="https://agentmods.dev/skills/skyf0xx/hedgehog/bmad-revendor"><img src="https://agentmods.dev/badge/skills/skyf0xx/hedgehog/bmad-revendor/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/skyf0xx/hedgehog/bmad-revendor"><img src="https://agentmods.dev/badge/skills/skyf0xx/hedgehog/bmad-revendor.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.00072 | $0.02378 |
| Opus 5 | $0.00036 | $0.01189 |
| Sonnet 5 | $0.00014 | $0.00476 |
| Haiku 4.5 | $0.00007 | $0.00238 |
Grade A, and why
bmad-revendor 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Re-vendoring BMAD-METHOD
vendor-skills/BMAD/ is a pinned, manually-updated vendor copy of eight skills
from bmad-code-org/BMAD-METHOD's bmm module (see
vendor-skills/BMAD/ATTRIBUTION.md for the current pin). It is never
auto-updated — re-vendoring is a deliberate act, run only when this
skill is invoked by name or the user explicitly asks to update BMAD.
What's vendored, and why these specific paths
Eight skill directories plus two shared scripts they all depend on:
src/core-skills/bmad-forge-idea— pressure-tests an idea before any artifact gets written; runs first in the shelf, ahead ofbmad-brainstorming. Carries its own script,resolve_personas.py(not shared with the other skills — vendored inside this skill's ownscripts/, not in the sharedvendor-skills/BMAD/scripts/).src/core-skills/bmad-brainstormingsrc/core-skills/bmad-advanced-elicitationsrc/core-skills/bmad-deep-reconsrc/bmm-skills/plan/bmad-product-briefsrc/bmm-skills/plan/bmad-prfaqsrc/bmm-skills/plan/bmad-prdsrc/bmm-skills/plan/bmad-uxsrc/scripts/memlog.py,src/scripts/resolve_customization.py— shared utilities every one of the eight skills calls. Not inside any single skill directory upstream; vendored separately intovendor-skills/BMAD/scripts/.
Upstream keeps the four bmm-skills above under a single flat
bmm-skills/plan/ directory as of the v6.11.0 vendor pass — it used to
be split across numbered 1-analysis/ and 2-plan-workflows/
directories. If upstream has moved them again since, update these paths
to match rather than leaving a stale layout here.
bmad-deep-recon was, before the v6.11.0 pass, the one skill in this
set that existed only on BMAD-METHOD's main branch — not in any tagged
release; it is now in v6.11.0. If a newer addition to this set is
ever unreleased, pin to main at a specific commit SHA rather than a
release tag (see "Pinning," below) instead of silently dropping it; ask
the user how to resolve the conflict if it's not obvious (this came up
during the original vendor pass — see git history on
vendor-skills/BMAD/).
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.
- 7d ago Changed · +4 lines 010ed007311b
- 11d ago First seen · 159 lines · 72 tokens per session scan A 7d701a551796
bmad-revendor is a skill published in the GitHub repository skyf0xx/hedgehog (38 stars, last pushed today), licensed MIT. It adds 72 tokens to every session and 2,378 once invoked, about $0.0004 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
writing-skills
Use when creating a new skill for the Shipworthy plugin, or when a recurring failure mode needs to be codified into a reusable guide. Covers TDD-for-documentation, CSO (Claude Search Optimization), adversarial testing, and the full skill lifecycle.
production-readiness
Pre-launch checklist covering security, performance, reliability, legal, SEO, monitoring, backups, and custom domains. Each item has both a plain-language explanation and technical implementation detail. Ensures nothing critical is missed before going live.
compliance-awareness
Practical engineering guidance for SOC 2, GDPR, HIPAA compliance and data classification. Covers access controls, audit logging, change management, right to deletion, data portability, consent, PHI encryption, and data classification levels. Engineering checks, not legal advice.
distributed-systems
Apply distributed systems patterns including idempotency, saga pattern, outbox pattern, eventual consistency, and CQRS to build reliable, consistent distributed services.
twelve-factor-app
Evaluate and apply the Twelve-Factor App methodology with modern 2025 interpretations. Covers all 12 factors with actionable checks for cloud-native applications running on containers, Kubernetes, and serverless platforms.
architecture-awareness
Detects project type, analyzes existing patterns, generates architecture specifications, and maintains architectural consistency across sessions. The key innovation that turns CLAUDE.md-style contracts into automatic, evolving project specifications.