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-branchgit 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-branch)<a href="https://agentmods.dev/commands/jpesewang/solo-dev-workflow/create-branch"><img src="https://agentmods.dev/badge/commands/jpesewang/solo-dev-workflow/create-branch.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.00000 | $0.00994 |
| Opus 5 | $0.00000 | $0.00497 |
| Sonnet 5 | $0.00000 | $0.00199 |
| Haiku 4.5 | $0.00000 | $0.00099 |
Grade A, and why
create-branch scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS -X POST \ How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are $DEV_ROLE, creating a new branch for the $PROJECT_NAME project with a Jira ticket ID.
IMPORTANT: Always ask for the Jira ticket ID before creating the branch.
When the user runs /create-branch, perform the following steps:
STEP 1: ASK FOR INFORMATION
Ask the user 2 questions:
- "Jira ticket ID? (e.g. PROJ-123)"
- The project has these Jira projects: read from
$JIRA_PROJECT_KEYSin config.env (Acme usesPROJ). - Validate input: it must match the regex
^(PROJECT_KEY)-\d+$where PROJECT_KEY belongs to $JIRA_PROJECT_KEYS. If not, ask again.
- The project has these Jira projects: read from
- "Short description for the branch? (e.g. add auth guard)"
STEP 2: CREATE BRANCH
See _shared/repo-conventions.md — the authoritative source, transcribed from
acme-mono/README.md.
Format:
PROJ-<ticket>-<short-description>
PROJ-fixed prefix, uppercase<ticket>— issue number, 1 to 3 digits<short-description>— kebab-case slug: letters, digits,.,_,-
This repo does NOT use a feature/ or fix/ type prefix, and no slash.
Examples:
PROJ-3-user-profile-screenPROJ-42-usage-analyticsPROJ-128-session-caching
Rejected:
- ❌
feature/PROJ-123-add-auth-guard— type prefix is not used in this repo - ❌
proj-3-user-profile-screen—PROJmust be uppercase - ❌
PROJ-1234-something— more than 3 digits
STEP 3: EXECUTE
Base branch is main. There is no dev branch in acme-mono.
[ -f ".claude/config.env" ] && source .claude/config.env
BASE="${PROJECT_BASE_BRANCH:-main}"
# Fetch latest
git fetch origin
# Checkout the base branch and pull latest before branching
git checkout "$BASE"
git pull origin "$BASE"
# Create the branch
git checkout -b {branch-name}
# Push the branch to remote
git push -u origin {branch-name}
STEP 4: JIRA COMMENT (automatic)
After creating the branch, comment on the Jira issue:
[ -f ".claude/config.env" ] && source .claude/config.env
source ~/.zshrc 2>/dev/null || true
if [ -z "$JIRA_TOKEN" ] || [ -z "$JIRA_EMAIL" ]; then
echo "[JIRA] WARN: \$JIRA_TOKEN or \$JIRA_EMAIL not set (.claude/config.env or ~/.zshrc) — skipping comment"
else
BASE_URL="$JIRA_BASE_URL"
curl -sS -X POST \
-H "Authorization: Basic $(echo -n "${JIRA_EMAIL}:${JIRA_TOKEN}" | base64)" \
-H "Content-Type: application/json" \
-d "{\"body\": \"Branch created: {branch-name}\"}" \
"${BASE_URL}/rest/api/3/issue/{TICKET_ID}/comment" > /dev/null && \
echo "[JIRA] Posted to {TICKET_ID}"
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 · 124 lines · 0 tokens per session scan A 4c007d2ecd23
create-branch is a command published in the GitHub repository jpeseWang/solo-dev-workflow (2 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 994 tokens. A static security scan graded it A with 1 finding (makes network calls). 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.