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 skills add DefaultPerson/agent-setup --skill push-and-prgit clone --depth 1 https://github.com/DefaultPerson/agent-setupWrote 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/skills/defaultperson/agent-setup/push-and-pr)<a href="https://agentmods.dev/skills/defaultperson/agent-setup/push-and-pr"><img src="https://agentmods.dev/badge/skills/defaultperson/agent-setup/push-and-pr/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/defaultperson/agent-setup/push-and-pr"><img src="https://agentmods.dev/badge/skills/defaultperson/agent-setup/push-and-pr.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00056 | $0.00308 |
| Opus 5.5 | $0.00022 | $0.00123 |
| Sonnet 5.5 | $0.00011 | $0.00062 |
| Haiku 4.5 | $0.00006 | $0.00031 |
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 1mo 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
State
!git status -sb 2>&1 | head -20
$ARGUMENTS
Conventions
- Use
gh. The base is the repository's default branch (gh repo view --json defaultBranchRef), never an assumedmain. - Rebase onto the base before pushing to keep history linear. Force-push only your own feature branch, and only with
--force-with-lease. - If the branch already has a PR, push to it instead of opening another one.
- PR title in Conventional Commit format, ≤72 chars; body sections: What, Why, How to test, Risks.
- Wait for checks only when the repository has them, and fix failures before merging.
- Merge only when the user asked for it: rebase-merge, delete the branch locally and on the remote, then update the local default branch with
git pull --rebase— rebase-merge rewrites commit SHAs. - On the default branch there is nothing to open a PR from: push directly only if the user asked to.
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.
- 1mo ago Changed · -24 lines · -5 tokens per session 91f5f6cf3a7e
- 1mo 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 12d ago), licensed MIT. It adds 56 tokens to every session and 308 once invoked, about $0.0002 per session on Opus 5.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
Use this skill whenever the user wants Claude Code on a Mac to notify an iPhone through Bark when a task, turn, or coding session finishes. Trigger on requests about Bark notifications, Claude completion alerts, iPhone push reminders, macOS to iPhone completion messages, Bark hook setup, or Bark troubleshooting, even…
bark-notify-setup
Set up Bark completion notifications for Claude Code on macOS by safely writing the local Bark sender script and merging a Stop hook into /.claude/settings.json. Use when the user explicitly asks to configure Bark for them or to directly install the completion notification flow.
conventional-commit
Rules for writing Conventional Commits messages in this project. MUST be invoked every time a commit is created.
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.
release-notes
Generate and publish concise, evidence-based notes in the body of the latest existing GitHub Release. Use only when the user explicitly invokes $release-notes or explicitly asks to update the latest existing GitHub Release body. Do not invoke for general release planning, changelog, tag, or version tasks.
ai-visibility-writing
Audit, question, suggest, or fact-preservingly revise a press release, blog post, contributed article, or expert explainer so AI answer systems can more easily retrieve, understand, quote, and cite its useful information. Use when someone asks for AI visibility, AI search, answer-engine, AEO, GEO, AI Overview, or…