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/pushgit clone --depth 1 https://github.com/jpeseWang/solo-dev-workflowWhat 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.00056 | $0.04993 |
| Opus 5 | $0.00028 | $0.02497 |
| Sonnet 5 | $0.00011 | $0.00999 |
| Haiku 4.5 | $0.00006 | $0.00499 |
Grade A, and why
push 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 2d 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 -u "$JIRA_EMAIL:$JIRA_TOKEN" -H "Accept: application/json" \ How it starts
The opening of the file, as written. The whole thing — 584 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are $DEV_ROLE working on $PROJECT_NAME (Acme). /push is the final step of a task: ensure the code is committed, push to remote, compute the actual work time, and log work to Jira.
STEP 1: LOAD ENV + CHECK BRANCH + CHECK JIRA TICKET
[ -f ".claude/config.env" ] && source .claude/config.env
source ~/.zshrc 2>/dev/null || true
CURRENT_BRANCH=$(git rev-parse --abbrev-ref HEAD)
1a. Guard: do not push directly to a protected branch
if [ "$CURRENT_BRANCH" = "dev" ] || [ "$CURRENT_BRANCH" = "main" ] || [ "$CURRENT_BRANCH" = "master" ]; then
echo "[ERROR] On branch '$CURRENT_BRANCH'. /push only runs on a feature branch."
echo " Checkout a feature branch first: git checkout <branch>"
exit 1
fi
echo "[BRANCH] $CURRENT_BRANCH"
1b. Extract the Jira ticket ID from the branch name
KEYS_REGEX=$(echo "$JIRA_PROJECT_KEYS" | tr ',' '|')
JIRA_ID=$(echo "$CURRENT_BRANCH" | grep -oE "(${KEYS_REGEX})-[0-9]+" | head -1)
If $JIRA_ID is non-empty → continue normally.
If $JIRA_ID is empty (the branch has no ticket, e.g. hotfix/fix-typo) → WARN and ask for confirmation:
⚠️ [JIRA] Branch '$CURRENT_BRANCH' has no Jira ticket ID.
The worklog will NOT be logged to Jira after the push.
The branch should follow the format: PROJ-{ticket}-{description}
e.g. PROJ-3-user-profile-screen, PROJ-42-usage-analytics
(acme-mono uses NO feature/ or fix/ prefix — see _shared/repo-conventions.md)
Do you still want to push?
[a] Push but skip the worklog (this branch doesn't need logging)
[b] Enter a ticket ID so work can still be logged (e.g. PROJ-123)
[c] Cancel — to change the branch name first
- [a] → set
SKIP_WORKLOG=true, continue pushing, after the push print simple output and exit - [b] → the user enters a ticket ID, set
JIRA_ID= input, continue normally - [c] → exit, do NOT push
1c. Check whether the commits on the branch belong to the user
# Check the author of the most recent commit on the branch
LAST_COMMIT_AUTHOR=$(git log -1 --format="%ae" HEAD)
GIT_USER_EMAIL=$(git config user.email)
if [ "$LAST_COMMIT_AUTHOR" != "$GIT_USER_EMAIL" ]; then
echo "⚠️ [AUTHOR] The most recent commit on this branch is not yours."
echo " Author: $LAST_COMMIT_AUTHOR | You: $GIT_USER_EMAIL"
echo " You may be pushing someone else's branch?"
echo " [a] Continue push + log work (you committed more)"
echo " [b] Continue push but SKIP log work"
echo " [c] Cancel"
# Let the user choose, handle accordingly
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.
- 2d ago First seen · 584 lines · 0 tokens per session scan A 83a1cbc83bdc
push is a command published in the GitHub repository jpeseWang/solo-dev-workflow (2 stars, last pushed 12d ago), licensed MIT. It adds 56 tokens to every session and 4,993 once invoked, about $0.0003 per session on Opus 5. 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.
constitution
Create or update the project constitution from interactive or provided principle inputs.