Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add choucrifahed/agent-plugins/plugin install bmad-githubWrote 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/choucrifahed/agent-plugins/bmad-github-story-setup-ci)<a href="https://agentmods.dev/skills/choucrifahed/agent-plugins/bmad-github-story-setup-ci"><img src="https://agentmods.dev/badge/skills/choucrifahed/agent-plugins/bmad-github-story-setup-ci.svg" alt="Measured on agentmods" height="20"></a>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.00075 | $0.00535 |
| Opus 5 | $0.00037 | $0.00267 |
| Sonnet 5 | $0.00015 | $0.00107 |
| Haiku 4.5 | $0.00007 | $0.00053 |
Grade A, and why
bmad-github-story-setup-ci 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.
What it actually says
Story Setup CI: Install BMAD Story Sync Workflow
You are installing a GitHub Actions workflow that automatically syncs GitHub issue closures back to BMAD files.
What the Workflow Does
- Trigger: Runs when a GitHub issue is closed
- Behavior: Looks up the closed issue in
github-issue-map.json, verifies a merged PR exists, then marks the corresponding story asdoneinsprint-status.yamland the story.mdfile. Also updates GitHub labels and checks for epic completion. - Config: Dynamically resolves the BMAD output folder at runtime by checking
_bmad/bmm/config.yaml, then_bmad/bmb/config.yaml, falling back to_bmad-output
Steps
1. Read the workflow template
Read the template file:
${CLAUDE_PLUGIN_ROOT}/references/bmad-story-sync.yml
Store its full contents — it will be written verbatim with no modifications.
2. Check if workflow already exists
Check whether .github/workflows/bmad-story-sync.yml already exists in the user's project.
If it exists, warn the user:
The file .github/workflows/bmad-story-sync.yml already exists.
Do you want to overwrite it with the latest template?
If the user declines, stop here.
3. Install the workflow
- Ensure the
.github/workflows/directory exists (create it if needed) - Write the template contents verbatim to
.github/workflows/bmad-story-sync.yml
4. Report
Tell the user:
Installed .github/workflows/bmad-story-sync.yml
This workflow triggers when a GitHub issue is closed and:
- Looks up the issue in github-issue-map.json
- Verifies a merged PR exists for the issue
- Marks the story as done in sprint-status.yaml and the story .md file
- Updates GitHub issue labels (adds status:done)
- Checks if all stories in the epic are done and updates epic status
- Commits and pushes the changes
No configuration needed — the workflow reads your BMAD config at runtime.
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 First seen · 61 lines · 75 tokens per session scan A 4a46ac171c7f
bmad-github-story-setup-ci is a skill published in the GitHub repository choucrifahed/agent-plugins (7 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 535 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-31.
Other skills, from other repositories
devops/deployment-process
A guide to releasing software through automated build, test, and deployment steps. CI/CD means automatically checking code and moving it through environments such as development, staging, and production.
qa/e2e-playwright
A method for writing Playwright end-to-end tests, which automate a browser to verify complete user journeys. It covers setup, reusable page objects, login reuse, API mocking, visual checks, multiple browsers and screen sizes, CI, and debugging.
backend/testing-guide
A guide for writing backend tests: small unit tests, tests that check connected parts such as an API and database, and end-to-end tests that follow a complete user flow.
architect/architecture-design
A guide to planning how a software system is organized, including its major parts, layers, folders, data, and API interfaces.
architect/data-api-design
A guide to designing data models and application programming interfaces (APIs), which are the rules software uses to exchange data.
backend/api-development
A guide to building web APIs, including resource URLs, request validation, consistent responses, error handling, authentication, and security.