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/jpesewang/solo-dev-workflow/create-mrgit clone --depth 1 https://github.com/jpeseWang/solo-dev-workflowWrote 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/commands/jpesewang/solo-dev-workflow/create-mr)<a href="https://agentmods.dev/commands/jpesewang/solo-dev-workflow/create-mr"><img src="https://agentmods.dev/badge/commands/jpesewang/solo-dev-workflow/create-mr.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.00030 | $0.01393 |
| Opus 5 | $0.00015 | $0.00696 |
| Sonnet 5 | $0.00006 | $0.00279 |
| Haiku 4.5 | $0.00003 | $0.00139 |
Grade A, and why
Create 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are $DEV_ROLE on Acme. This skill opens a GitHub pull request for the current branch.
Repo: [email protected]:acme-org/acme-mono.git
Conventions come from _shared/repo-conventions.md, transcribed from the repo README.
The previous GitLab implementation was removed in v2.1.0 — this project has never used
GitLab, and the GitLab env vars are gone from .claude/config.env.
The flow
[ -f ".claude/config.env" ] && source .claude/config.env
BASE="${PROJECT_BASE_BRANCH:-main}"
BRANCH=$(git rev-parse --abbrev-ref HEAD)
# 1. Never open a PR from the base branch itself
if [ "$BRANCH" = "$BASE" ]; then
echo "[ERROR] You are on $BASE. Create a PROJ-<ticket>-<slug> branch first."; exit 1
fi
# 2. Branch name must match the repo convention
if ! echo "$BRANCH" | grep -qE '^PROJ-[0-9]{1,3}-[A-Za-z0-9._-]+$'; then
echo "[ERROR] Branch '$BRANCH' does not match PROJ-<1-3 digits>-<slug>."
echo " This repo uses no feature/ or fix/ prefix."; exit 1
fi
# 3. Must have something to review
git rev-parse @{u} >/dev/null 2>&1 || git push -u origin "$BRANCH" || exit 1
if [ "$(git log "origin/$BASE..HEAD" --oneline | wc -l | tr -d ' ')" = "0" ]; then
echo "[ERROR] No commits ahead of $BASE. Nothing to open."; exit 1
fi
# 4. Authenticate gh with the classic PAT — NOT `gh auth login`
export GH_TOKEN="$GITHUB_TOKEN"
if [ -z "$GH_TOKEN" ]; then
echo "[ERROR] \$GITHUB_TOKEN is empty in .claude/config.env"
echo " Create a CLASSIC token with scope 'repo':"
echo " https://github.com/settings/tokens"
exit 1
fi
gh auth status >/dev/null 2>&1 || { echo "[ERROR] GH_TOKEN rejected by GitHub"; exit 1; }
⚠️ Do not use
gh auth login's browser flow. Theacme-orgorg has OAuth App access restrictions enabled, which blocks third-party OAuth apps — this is what makes HTTPSgit clonefail with "Repository not found". A classic PAT with thereposcope is not subject to that restriction. Export it asGH_TOKENandghpicks it up.
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 · 135 lines · 30 tokens per session scan A 82c9498cd3ce
Create Pull Request is a command published in the GitHub repository jpeseWang/solo-dev-workflow (2 stars, last pushed 13d ago), licensed MIT. It adds 30 tokens to every session and 1,393 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.