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 commands/yassinello/claude-plugin-prd-workflow/sync-githubgit clone --depth 1 https://github.com/Yassinello/claude-plugin-prd-workflowWhat 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.00015 | $0.02083 |
| Opus 5 | $0.00008 | $0.01042 |
| Sonnet 5 | $0.00003 | $0.00417 |
| Haiku 4.5 | $0.00002 | $0.00208 |
Grade A, and why
sync-github 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 2d 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 — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync GitHub Command
Synchronize PRDs with GitHub Issues for team collaboration.
Purpose
Enable bidirectional sync between PRDs and GitHub Issues:
- Create GitHub Issues from PRDs
- Update PRD status when Issues close
- Link PRDs to Issues for easy access
- Enable team collaboration outside Claude Code
Usage
Create GitHub Issue from PRD
/sync-github PRD-003
Creates a GitHub Issue with:
- Title: "PRD-003: Feature Name"
- Body: Full PRD markdown
- Labels: Priority (P0/P1/P2) + "feature" + "PRD-003"
- Adds issue link to PRD metadata
Options
# Specify assignee
/sync-github PRD-003 --assignee=johndoe
# Add to milestone
/sync-github PRD-003 --milestone=v2.0
# Custom labels
/sync-github PRD-003 --labels=backend,api,urgent
# Skip confirmation
/sync-github PRD-003 --yes
Workflow
Step 1: Verify Prerequisites
Check that:
- GitHub CLI (
gh) is installed and authenticated - User is in a git repository
- PRD exists and is readable
- PRD not already synced (unless
--force)
# Check gh auth
gh auth status
# If not authenticated, prompt user
gh auth login
Step 2: Read PRD Content
Load PRD file and extract metadata:
- PRD ID (e.g., PRD-003)
- Feature name
- Status
- Priority (P0/P1/P2/P3)
- Full markdown content
Step 3: Create GitHub Issue
Use GitHub CLI to create issue:
gh issue create \
--title "PRD-003: Feature Name" \
--body "$(cat prd_content.md)" \
--label "P0,feature,PRD-003" \
--assignee "johndoe" \
--milestone "v2.0"
Step 4: Update PRD with Issue Link
Add to PRD metadata section (after Priority):
**Priority**: P0
**GitHub Issue**: #42 (https://github.com/org/repo/issues/42)
**Synced**: 2025-10-26
Step 5: Setup Bidirectional Sync (Optional)
Ask user if they want automatic status sync:
✅ GitHub Issue #42 created
🔗 Bidirectional sync available:
• When issue closes → PRD moves to complete automatically
• When PRD completes → Issue closes automatically
Enable? [Y/n]
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.
- 2d ago First seen · 336 lines · 15 tokens per session scan A 9bd78e4e4155
sync-github is a command published in the GitHub repository Yassinello/claude-plugin-prd-workflow (12 stars, last pushed 9mo ago), licensed MIT. It adds 15 tokens to every session and 2,083 once invoked, about $0.0001 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 commands, from other repositories
simplify
The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
VibeGuard: ExecPlan
Long-term task execution plan — generates self-contained execution documents from SPEC, supports cross-session recovery.
VibeGuard: Review
Structured code review - first run the guard to obtain the baseline, then review according to security → logic → quality → performance priority.
help
Category: System Syntax: /help [command|topic].
remediate
Close the debt the deterministic lanes cannot version-bump away: the grandfathered broken build, advisories with no direct upgrade path, the lint backlog, missing tests, missing docs. Each run plans that debt as finite work orders and works them in two tiers: deterministic recipes execute first at $0 (lockfile resync…