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/commitnpx skills add DefaultPerson/agent-setup --skill commitgit 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.00064 | $0.00546 |
| Opus 5 | $0.00032 | $0.00273 |
| Sonnet 5 | $0.00013 | $0.00109 |
| Haiku 4.5 | $0.00006 | $0.00055 |
Grade A, and why
commit 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 yesterday.
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 - Diff: !
git diff HEAD - Branch: !
git branch --show-current - Recent commits: !
git log --oneline -10
$ARGUMENTS
Arguments: [optional commit header]
Git Rules
- Conventional Commits:
<type>[scope][!]: <short summary> - Types:
feat,fix,docs,refactor,perf,test,chore,build,ci,revert - English only, title ≤72 characters
- One commit — one purpose. Split different concerns into separate commits.
- Never commit secrets: tokens, keys,
.env, database dumps, PII - Prefer feature branches (
feat/<name>,fix/<name>,chore/<name>) over committing tomain
Algorithm
- Guard:
git status— if clean, stop ("Nothing to commit"). If branch ismain— ask user (AskUserQuestion): "You're on main. Commit directly or create a feature branch?" If user says branch — help create one and switch. - Header:
- If argument provided — use it (validate format).
- Otherwise — inspect changes, generate a Conventional Commit header.
- Validate: matches
<type>[scope][!]: <summary>, ≤72 chars, English.
- Stage & Commit:
git add -A→git commit -m "<header>"(add body/footer if multi-concern change warrants it). - Output:
Committed "<header>". - Chain to push: if the original user request contains any of
and push,и пуш,+ pr,and pr,и пр,сделай пр,push it— immediately execute thepush-and-prskill algorithm without re-asking for confirmation (except the merge step inside push-and-pr). Otherwise — briefly suggest/push-and-pron the next line and stop.
Act immediately — no confirmation needed.
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.
- yesterday First seen · 43 lines · 64 tokens per session scan A 3ec5ba393865
commit is a skill published in the GitHub repository DefaultPerson/agent-setup (11 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 546 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.
webmcp-setup
Bootstraps webmcp-react into an existing React or Next.js app. Installs dependencies, adds WebMCPProvider, creates a first tool, and configures the MCP client bridge. Use when the user wants to set up WebMCP, add MCP tools to their app, integrate webmcp-react, or make their React app accessible to AI agents.