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 agentmods add skills/choucrifahed/agent-plugins/bmad-github-story-syncnpx skills add choucrifahed/agent-plugins --skill bmad-github-story-syncgit clone --depth 1 https://github.com/choucrifahed/agent-pluginsWrote 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-sync)<a href="https://agentmods.dev/skills/choucrifahed/agent-plugins/bmad-github-story-sync"><img src="https://agentmods.dev/badge/skills/choucrifahed/agent-plugins/bmad-github-story-sync.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 | $0.00081 | $0.02134 |
| Opus 5 | $0.00041 | $0.01067 |
| Sonnet 5 | $0.00016 | $0.00427 |
| Haiku 4.5 | $0.00008 | $0.00213 |
Grade A, and why
bmad-github-story-sync 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 5d 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Story Sync: Reconcile GitHub State → BMAD Files (on main) + Local Worktree Cleanup
This skill brings sprint-status.yaml and story files on main into agreement with GitHub issue state, and cleans up
local worktrees/branches for stories whose PRs have merged.
GitHub issue status:* labels are the authoritative store for cross-agent coordination. sprint-status.yaml is
BMAD's own tracker — other BMAD workflows (and other plugins) read it. This skill keeps it current as a courtesy to BMAD.
Writes happen on main (this skill is always run from main, so writes/commits there are not a coordination
problem and do not block parallel agents working in worktrees).
The bmad-story-sync GitHub Actions workflow (installed via /story-setup-ci) performs the same writes automatically
on every PR merge. Both writers are idempotent — if both run, the second is a no-op. If a user hasn't installed the CI
workflow (or it failed), running /story-sync is the reliable manual path.
IMPORTANT: This skill MUST be run from the main repo directory, on main.
Pre-flight Checks
-
Verify you are in the main repo (not a worktree):
git rev-parse --show-toplevel git rev-parse --git-common-dir git rev-parse --git-dirIf
--git-dirdiffers from--git-common-dir, you're in a linked worktree. STOP and tell the user to run this from the main repo directory. -
Verify you are on
main:git branch --show-currentIf not on
main, warn the user and ask if they want to proceed. -
Pull latest (brings in any CI-authored sprint-status.yaml updates):
git pull --rebase -
Verify
ghCLI is authenticated:gh auth status
Phase 1: Resolve Worktree Root
Read and follow ${CLAUDE_PLUGIN_ROOT}/references/resolve-worktree-root.md.
Phase 2: Read Current State
- Read the GitHub issue map:
Read
<output_folder>/implementation-artifacts/github-issue-map.json- Maps story keys (e.g.,
"1-2") to GitHub issue numbers and URLs. - If the file doesn't exist, STOP and tell the user to run Story Init (SI) first.
- Maps story keys (e.g.,
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.
- 5d ago First seen · 248 lines · 81 tokens per session scan A 62d49c4fef58
bmad-github-story-sync is a skill published in the GitHub repository choucrifahed/agent-plugins (7 stars, last pushed 1mo ago), licensed MIT. It adds 81 tokens to every session and 2,134 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
qa/e2e-playwright
Playwright E2E 测试完整方法论，涵盖项目初始化、Page Object Model、认证复用、API Mock、视觉回归、多浏览器测试、CI 集成和调试技巧.
backend/testing-guide
后端测试编写指南，包括单元测试、集成测试和E2E测试的编写方法和最佳实践.
architect/architecture-design
系统架构设计方法论，包含架构模式选择、系统分层、目录结构设计.
architect/data-api-design
Skill "architect/data-api-design" from echoVic/boss-skill, covering 数据模型与api设计方法论, 适用场景, 数据模型设计, 1. 实体识别 and 2. 关系识别.
backend/api-development
后端API开发方法论，包括RESTful/GraphQL设计、请求验证、错误处理和安全实现.
ui-designer/component-specification
UI组件规范，定义按钮、输入框、卡片等基础组件的变体、尺寸、状态.