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/amitgurbani/mcp-server-woocommerce/commitgit clone --depth 1 https://github.com/AmitGurbani/mcp-server-woocommerceWhat 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.00007 | $0.00751 |
| Opus 5 | $0.00003 | $0.00376 |
| Sonnet 5 | $0.00001 | $0.00150 |
| Haiku 4.5 | $0.00001 | $0.00075 |
Grade A, and why
commit 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a git commit following the project's conventional commit format with emoji prefixes.
Commit Message Format
<type>(<scope>): <emoji> <subject>
[optional body]
[optional footer]
Types and Emojis
feat: ✨ New featurefix: 🐛 Bug fixdocs: 📝 Documentation changesstyle: 💄 Code style/formatting (no logic changes)refactor: ♻️ Code refactoringperf: ⚡ Performance improvementstest: ✅ Adding or updating testschore: 🔧 Maintenance tasks, dependenciesci: 👷 CI/CD changesbuild: 📦 Build system changesrevert: ⏪ Revert previous commit
Scopes
Common scopes in this project:
tools- MCP tool files (products, orders, categories, etc.)services- Base service layer, WooCommerce clientserver- Server setup, entry pointconfig- tsconfig, package.json, .mcp.jsondeps- Dependency updates
CRITICAL: No Attribution in Commits
DO NOT add any Claude Code attribution to commit messages.
Commit messages must be clean and end after the optional body/footer. Never include:
- ❌ "Generated with Claude Code"
- ❌ "Co-Authored-By: Claude"
- ❌ Links to claude.com
- ❌ Any other attribution lines
The commit message should contain ONLY:
- ✅ Type, scope, emoji, and subject line
- ✅ Optional body explaining "why"
- ✅ Optional footer (issue references, breaking changes)
Instructions
- Run
git statusto see what files are staged/modified - Run
git diff --stagedto review staged changes - Run
git log --oneline -10to see recent commit style - Analyze the changes and determine:
- Type (feat, fix, docs, etc.)
- Scope (which area affected)
- Clear, concise subject line (50 chars max)
- Body if needed to explain "why" not "what"
- Stage any unstaged files that should be included:
git add <files> - Create the commit with proper format (NO ATTRIBUTION!)
- Run
git statusafter committing to confirm
Examples
# New MCP tool
git commit -m "feat(tools): ✨ add product variation tools"
# Bug fix in service layer
git commit -m "fix(services): 🐛 handle WooCommerce API timeout errors"
# Documentation update
git commit -m "docs(config): 📝 update CLAUDE.md with new tools"
# Dependency upgrade
git commit -m "chore(deps): ⬆️ upgrade zod to v4"
# Refactoring
git commit -m "refactor(services): ♻️ extract pagination logic to helper"
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 · 102 lines · 7 tokens per session scan A 9348a2e61473
commit is a command published in the GitHub repository AmitGurbani/mcp-server-woocommerce (2 stars, last pushed 4mo ago), licensed MIT. It adds 7 tokens to every session and 751 once invoked, about $0.0000 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 commands, from other repositories
push
You are creating a commit for the user. Follow these steps EXACTLY.
codexreview
You are a hostile code reviewer. Your job is to find bugs, vulnerabilities, and defects. Not to compliment code.
example-command
TODO — one-line description shown in the slash-command picker.
qland
Quick-land — commit WIP, sync onto main, squash-merge WITHOUT running the gate. For burst-landing many in-flight worktrees under gate congestion; finish the burst with one /go (full gate + deploy). Run from inside a feature worktree.
cleanup-issues
Clean up GitHub issues by aligning prefixes with commitlint conventions and adding appropriate labels based on content.
git
Git operations with intelligent commit messages and workflow optimization.