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/waterplanai/agentic-config/ac-git-pull-requestnpx skills add WaterplanAI/agentic-config --skill ac-git-pull-requestgit clone --depth 1 https://github.com/WaterplanAI/agentic-configWhat 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.00035 | $0.02646 |
| Opus 5 | $0.00017 | $0.01323 |
| Sonnet 5 | $0.00007 | $0.00529 |
| Haiku 4.5 | $0.00003 | $0.00265 |
Grade A, and why
ac-git-pull-request 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 3d 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 — 395 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Request Creator
Creates a comprehensive GitHub Pull Request with authentication validation and structured documentation.
Usage
/skill:ac-git-pull-request [target_branch] [gh_user]
Arguments:
target_branch: Base branch for PR (default:main)gh_user: Expected GitHub username (default:$GH_USERenv var)
Examples:
/skill:ac-git-pull-request # Uses main, $GH_USER
/skill:ac-git-pull-request master # Target master branch
/skill:ac-git-pull-request main my-username # Explicit user override
Workflow Steps
Step 1: Authentication Verification (CRITICAL - DO FIRST)
INSTRUCTION: Verify GitHub CLI authentication before any other operation.
ROOT=$(git rev-parse --show-toplevel)
BRANCH=$(git rev-parse --abbrev-ref HEAD)
# Get authenticated user
echo "Checking GitHub authentication..."
GH_AUTH_OUTPUT=$(gh auth status 2>&1)
echo "$GH_AUTH_OUTPUT"
# Extract authenticated username
AUTH_USER=$(echo "$GH_AUTH_OUTPUT" | grep -oE "Logged in to github.com account [^ ]+ " | sed 's/Logged in to github.com account //' | tr -d ' ' || echo "")
# Alternative extraction if format differs
if [ -z "$AUTH_USER" ]; then
AUTH_USER=$(echo "$GH_AUTH_OUTPUT" | grep -oE "account [^(]+" | head -1 | sed 's/account //' | tr -d ' ')
fi
echo "Authenticated as: $AUTH_USER"
Validation Logic:
- Extract
AUTH_USERfromgh auth statusoutput - Determine expected user:
- If
gh_userargument provided -> use it - Else if
$GH_USERenv var set -> use it - Else -> skip user validation (proceed with warning)
- If
- Compare
AUTH_USERwith expected user - If mismatch: STOP immediately with error:
ERROR: GitHub authentication mismatch - Authenticated as: <AUTH_USER> - Expected user: <EXPECTED_USER> Please run: gh auth login Or switch accounts: gh auth switch - If match: Proceed with success message
Step 2: Pre-Flight Validation
# Check not on protected branch
if [ "$BRANCH" = "master" ] || [ "$BRANCH" = "main" ]; then
echo "ERROR: Cannot create PR from protected branch: $BRANCH"
exit 1
fi
# Determine target branch
TARGET="${1:-main}" # Default to main
# Verify target exists on remote
if ! git -C "$ROOT" show-ref --verify --quiet "refs/remotes/origin/$TARGET"; then
echo "ERROR: Target branch 'origin/$TARGET' does not exist"
echo "Available remote branches:"
git -C "$ROOT" branch -r | grep -v HEAD
exit 1
fi
# Check for uncommitted changes
if [ -n "$(git -C "$ROOT" status --porcelain)" ]; then
echo "WARNING: Uncommitted changes detected"
git -C "$ROOT" status --short
fi
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.
- 3d ago First seen · 395 lines · 35 tokens per session scan A 86c4f16c09db
ac-git-pull-request is a skill published in the GitHub repository WaterplanAI/agentic-config (30 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 2,646 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.
Other skills, from other repositories
curate-a-team-library
Use when building a managed team skills library for a real stack. Map work to shelves, browse before curating, write meaningful whyHere notes, and create a starter pack once the first pass is solid.
migrate-skills-between-libraries
Use when moving skills between library workspaces or upgrading from a personal library to a team library. Export from one workspace, import into another.
review-a-skill
Use when evaluating whether a skill belongs in a library. Preview content, check frontmatter, validate structure, and decide whether to keep, curate, or remove.
audit-library-health
Use when checking the overall health of a skills library. Run doctor, validate, check for stale skills, and verify generated docs are in sync.
browse-and-evaluate
Use when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to limit output size and --dry-run before committing to an install.
install-from-remote-library
Use when installing skills from a shared ai-agent-skills library repo. Inspect with --list first, prefer --collection, and preview with --dry-run before installing.