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 skills add dr-robert-li/cowork-wordpress-expert --skill build-gitgit clone --depth 1 https://github.com/dr-robert-li/cowork-wordpress-expertWrote 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/dr-robert-li/cowork-wordpress-expert/build-git)<a href="https://agentmods.dev/skills/dr-robert-li/cowork-wordpress-expert/build-git"><img src="https://agentmods.dev/badge/skills/dr-robert-li/cowork-wordpress-expert/build-git/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/dr-robert-li/cowork-wordpress-expert/build-git"><img src="https://agentmods.dev/badge/skills/dr-robert-li/cowork-wordpress-expert/build-git.svg" alt="Reviewed on agentmods" width="80" 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.00031 | $0.03328 |
| Opus 5.5 | $0.00012 | $0.01331 |
| Sonnet 5.5 | $0.00006 | $0.00666 |
| Haiku 4.5 | $0.00003 | $0.00333 |
Grade A, and why
build-git 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 1mo 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 — 354 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Git Skill
Initializes a git repository at the build root directory, writes a two-phase .gitignore that excludes WordPress core and known reinstallable components while tracking custom-generated content, and provides a commit helper for staged commits after each build skill stage.
This skill runs at multiple points throughout the build pipeline — not as a single step. Git init happens early (after directory setup), .gitignore Phase 1 is written before any commits, .gitignore Phase 2 is appended after build-content, and commits happen after each skill stage.
This skill expects the following variables to be set by the calling command before invocation:
BUILD_DIR— absolute path to the build directory (set by build-scaffold Section 2)THEME_SLUG— theme directory slug (required for Section 3, set by build-theme)INSTALLED_PLUGINS— array ofslug:name:versionentries (required for Section 3, set by build-content)MCP_ADAPTER_VERSION— MCP adapter version string (required for Section 5 commit messages, set by build-mcp)THEME_NAME— display name of installed theme (required for Section 5 commit messages, set by build-theme)SLUG— build slug used as the build(init) commit subject (set in Section 1 of COMMAND.md)PAGES_CREATED— count of pages created (required for Section 5 commit body, set by build-content)POSTS_CREATED— count of posts created (required for Section 5 commit body, set by build-content)
Section 1: Git Initialization and User Config
Initialize a git repository at the build root and configure a fallback git identity if none is globally set.
Runs ONCE, after build-scaffold Section 2 (directory setup), BEFORE WP core download.
echo "[Build] Initializing git repository at $BUILD_DIR..."
echo ""
# Initialize git at build root with main as default branch
if git -C "$BUILD_DIR" init -b main > /dev/null 2>&1; then
echo "[Build] Git initialized at $BUILD_DIR (branch: main)"
else
echo "[Build] WARNING: git init failed at $BUILD_DIR. Git versioning will be skipped."
echo "[Build] WARNING: Build will continue without git history."
GIT_INITIALIZED=false
fi
# Check for existing git user config — set project-level fallback if missing
if [ "${GIT_INITIALIZED:-true}" = "true" ]; then
GIT_USER_NAME=$(git config --global user.name 2>/dev/null || echo "")
GIT_USER_EMAIL=$(git config --global user.email 2>/dev/null || echo "")
if [ -z "$GIT_USER_NAME" ] || [ -z "$GIT_USER_EMAIL" ]; then
git -C "$BUILD_DIR" config user.name "CoWork Build"
git -C "$BUILD_DIR" config user.email "[email protected]"
echo "[Build] NOTE: No global git user config found. Using project-level fallback: CoWork Build <[email protected]>"
echo "[Build] NOTE: Run 'git config --global user.name \"Your Name\"' to set your own identity."
else
echo "[Build] Git user: $GIT_USER_NAME <$GIT_USER_EMAIL>"
fi
GIT_INITIALIZED=true
fi
echo ""
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.
- 1mo ago First seen · 354 lines · 31 tokens per session scan A 145cfaff2b61
build-git is a skill published in the GitHub repository dr-robert-li/cowork-wordpress-expert (29 stars, last pushed 8mo ago), licensed MIT. It adds 31 tokens to every session and 3,328 once invoked, about $0.0001 per session on Opus 5.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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…