build-git

build-git is a skill for Claude Code from dr-robert-li/cowork-wordpress-expert. It costs 31 tokens per session (3,328 once invoked), scanned A, original, MIT.

A build-stage Git helper for WordPress projects. It initializes a repository, creates a generated .gitignore that leaves out WordPress core and reinstallable components, and commits completed build stages.

In plain words
What is it for?
Use it during a WordPress build to initialize Git, update ignore rules, and create commits after scaffold, theme, content, and related build stages.
Why use it?
It keeps generated project history organized while avoiding commits of files that can be reinstalled. Conventional commit prefixes make the build stages easier to identify.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument.

Part of the wordpress-expert plugin — 54 skills shipped together

Good fit Use it during a WordPress build to initialize Git, update ignore rules, and create commits after scaffold, theme, content, and related build stages.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dr-robert-li/cowork-wordpress-expert/build-git
Install

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.

Any agent
npx skills add dr-robert-li/cowork-wordpress-expert --skill build-git
Clone the repo
git clone --depth 1 https://github.com/dr-robert-li/cowork-wordpress-expert

Made for: Claude Code.

Or install wordpress-expert, the plugin that ships this one along with the rest of its 54 skills.

Wrote 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.

agentmods badge for build-git

README.md
[![agentmods](https://agentmods.dev/badge/skills/dr-robert-li/cowork-wordpress-expert/build-git.svg)](https://agentmods.dev/skills/dr-robert-li/cowork-wordpress-expert/build-git)
Your own site
<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="Measured on agentmods" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,328 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.03328
Opus 5 $0.00015 $0.01664
Sonnet 5 $0.00006 $0.00666
Haiku 4.5 $0.00003 $0.00333

Measured 8d ago against content hash 145cfaff2b61, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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 8d 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.

skills/build-git/SKILL.md · 354 lines

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 of slug:name:version entries (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 ""

Read the full file on GitHub · 354 lines

Changes

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.

  1. 8d ago First seen · 354 lines · 31 tokens per session scan A 145cfaff2b61

Subscribe to this mod's changes

build-git is a skill published in the GitHub repository dr-robert-li/cowork-wordpress-expert (28 stars, last pushed 6mo ago), licensed MIT. It adds 31 tokens to every session and 3,328 once invoked, about $0.0002 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.