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/mralaminahamed/wp-dev-skills/wp-github-flownpx skills add mralaminahamed/wp-dev-skills --skill wp-github-flowgit clone --depth 1 https://github.com/mralaminahamed/wp-dev-skillsWrote 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/mralaminahamed/wp-dev-skills/wp-github-flow)<a href="https://agentmods.dev/skills/mralaminahamed/wp-dev-skills/wp-github-flow"><img src="https://agentmods.dev/badge/skills/mralaminahamed/wp-dev-skills/wp-github-flow.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.00290 | $0.04643 |
| Opus 5 | $0.00145 | $0.02322 |
| Sonnet 5 | $0.00058 | $0.00929 |
| Haiku 4.5 | $0.00029 | $0.00464 |
Grade A, and why
wp-github-flow 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 4d 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 — 342 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Contribution Flow
Model note: Issue-driven mode (root-cause tracing + fix) requires
sonnetoropus. Changes-driven mode (group + commit existing edits) is mechanical and works well onhaiku.
Overview
Two entry modes that converge on the same shipping flow (branch → scoped commits → push → PR):
- Issue-driven — fetch issue → trace root cause → fix → ship. Wraps
superpowers:systematic-debugging. Root cause MUST be confirmed before any fix is written. - Changes-driven — read the working tree → group changes by conventional-commit scope → one commit per scope → ship. No issue required.
Both end at §6 Branch, Commit, PR, which is shared.
When to use
Issue-driven:
- User says "analyze/debug/fix/investigate issue #NNN"
- User pastes a GitHub issue URL and asks to debug it
- User says "find the root cause of this bug" with an issue reference
Changes-driven:
- "commit my changes", "commit these scope by scope", "commit by scope"
- "create a branch and PR", "open a PR for these changes"
- "read all changes from X and commit + create PR"
- Any request whose end goal is commits/branch/PR from existing working-tree edits
Not for: Plugin version releases or WP.org SVN deploy — use wp-plugin-release and wp-org-submission. QA failure triage on an already-open PR — use wp-ci-qa.
Required Sub-Skill
Issue-driven only: Invoke superpowers:systematic-debugging before any fix. Do NOT skip Phase 1 (root cause investigation). Changes-driven mode skips this — the edits already exist.
References
references/gh-reference.md—ghCLI commands, branch naming rules, label discovery, PR template sections, common CI failuresreferences/project-entry-points.md— project layout template: repos, plugin dirs, entry-point files, and key conventions; copy and fill in for your projectreferences/conventional-commits.md— type/scope table, WP-specific scope list, summary rules, multi-commit PR rules, footer conventions, rebase reword
What ships with it
4 files 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.
- 4d ago First seen · 342 lines · 290 tokens per session scan A 01a18828c555
wp-github-flow is a skill published in the GitHub repository mralaminahamed/wp-dev-skills (27 stars, last pushed 1mo ago), licensed MIT. It adds 290 tokens to every session and 4,643 once invoked, about $0.0014 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
woocommerce-markdown
Guidelines for creating and modifying markdown files in WooCommerce. Use when writing documentation, README files, or any markdown content.
woocommerce-code-review
Review WooCommerce code changes for coding standards compliance. Use when reviewing code locally, performing automated PR reviews, or checking code quality.
woocommerce-git-draft-pr
Create a high-quality draft PR for the current branch. Use when the user says "create a PR", "draft PR", "open a PR", "make a PR", "push and create PR", or "submit PR".
woocommerce-local-env
Set up, start, stop, restart, verify, and troubleshoot the WooCommerce Core local development environment with wp-env and asset build watchers. Use when Codex is asked to run WooCommerce locally, prepare wp-env, watch WooCommerce builds, choose between full and targeted build/watch commands, diagnose localhost:8888…
woocommerce-email-editor
Setup and develop the WooCommerce block email editor. Use when working on email templates, transactional emails, or the email editor feature.
woocommerce-git-commit
Commit uncommitted changes with well-crafted messages following WooCommerce repo conventions. Use when the user says "commit", "commit changes", "commit this", "git commit", or "save my work".