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/defaultperson/agent-setup/push-and-prnpx skills add DefaultPerson/agent-setup --skill push-and-prgit clone --depth 1 https://github.com/DefaultPerson/agent-setupWhat 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.00061 | $0.00616 |
| Opus 5 | $0.00030 | $0.00308 |
| Sonnet 5 | $0.00012 | $0.00123 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
push-and-pr 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.
What it actually says
Context
- Status: !
git status - Branch: !
git branch --show-current - Remote: !
git remote -v - Unpushed commits: !
git log @{u}..HEAD --oneline 2>/dev/null || echo "No upstream set"
Git Rules
- Trunk-based development with rebase (linear history)
- PR title = Conventional Commit format, ≤72 chars
- PR description: what / why / how to test / risks
- PR base always
main, merge strategy: Rebase and merge --force-with-leaseonly on personal feature branches after rebase- Use
ghfor all GitHub operations - Large PRs (>400 LOC) — consider splitting
Algorithm
- Guard:
git status— ensure working tree is clean (everything committed).- If on
main: ask user (AskUserQuestion): "You're on main. Push directly or create a feature branch for PR?"- Push directly:
git push origin main→ output "Pushed to main." STOP. - Create branch: help create feature branch, switch to it, then continue.
- Push directly:
- If on feature branch: continue.
- If on
- Sync:
git fetch origin→git rebase origin/main→git push -u origin HEAD --force-with-lease. - PR:
- Check if PR exists:
gh pr view --json number— if exists, just push updates. - Create:
gh pr create --base main --head <current-branch>. - Title: Conventional Commit format.
- Body: what / why / how to test / risks.
- Check if PR exists:
- Checks:
gh pr checks --watch— if failing, diagnose and fix, re-push. - Review: Review using repo's PR template/checklist if present.
- Merge: All checks green → ask user (AskUserQuestion): "Merge and delete branch?"
- Yes:
gh pr merge --rebase→git switch main && git pull origin main→git branch -D <branch> && git push origin --delete <branch>. - No: output PR link and stop.
- Yes:
- Output: PR link, check statuses, summary of what was done.
Act immediately — no confirmation needed (except merge step).
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 · 49 lines · 61 tokens per session scan A ab4a597b4832
push-and-pr is a skill published in the GitHub repository DefaultPerson/agent-setup (11 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 616 once invoked, about $0.0003 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
bark-notify-test
Send a Bark verification notification for the current Claude Code Bark setup on macOS or Windows. Use when the user wants to test delivery, confirm encryption works, or check whether the configured completion notification is healthy.
bark-notify
Use this skill whenever the user wants Claude Code to notify an iPhone through Bark when a task, turn, or coding session finishes. Works on macOS, Linux, and Windows. Trigger on requests about Bark notifications, Claude completion alerts, iPhone push reminders, completion messages, Bark hook setup, or Bark…
bark-notify-setup
Set up Bark completion notifications for Claude Code on macOS or Windows by safely writing the local Bark sender script and merging hooks into /.claude/settings.json. Use when the user explicitly asks to configure Bark for them or to directly install the completion notification flow.
bark-notify-uninstall
Remove Bark notification configuration from Claude Code on macOS, Linux, or Windows. Use when the user wants to uninstall, remove, or clean up Bark notifications, delete the Bark hook, or reset their Bark setup.
at-vision
Inspect screenshots, photos, diagrams, image paths, and image URLs when the task depends on visible content. Use when the prompt lacks actual image content, native inspection fails, or the user requests inspectimage; prefer the MCP tool, then the installed CLI.
decision-ledger
Maintain an append-only decision ledger (DECISIONS.md). Use when the user confirms a decision, reverses or changes a past decision, asks what was decided and why, or at session start to load standing decisions.