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 commitgit 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/commit)<a href="https://agentmods.dev/skills/defaultperson/agent-setup/commit"><img src="https://agentmods.dev/badge/skills/defaultperson/agent-setup/commit/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/commit"><img src="https://agentmods.dev/badge/skills/defaultperson/agent-setup/commit.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.00061 | $0.00312 |
| Opus 5.5 | $0.00024 | $0.00125 |
| Sonnet 5.5 | $0.00012 | $0.00062 |
| Haiku 4.5 | $0.00006 | $0.00031 |
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 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 -40
!git diff --stat HEAD 2>/dev/null | tail -25
!git log --oneline -8 2>/dev/null | cat
Requested header (may be empty): $ARGUMENTS
Conventions
- Conventional Commits:
<type>(<scope>)!: <summary>— English, imperative, ≤72 chars. - One purpose per commit: split unrelated changes into separate commits.
- Stage paths explicitly. Never
git add -Aorgit add .— they sweep in untracked junk and secrets. - Never commit secrets,
.envfiles, dumps or build output. - On the repository's default branch, create a feature branch first (
feat/…,fix/…,chore/…) unless the user asked to commit there.
If the request also asks to push or open a PR ("и пуш", "and push", "сделай пр"), continue with the push-and-pr skill.
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 · -15 lines · -3 tokens per session 2ec26db575ba
- 1mo ago 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 12d ago), licensed MIT. It adds 61 tokens to every session and 312 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
setup-pre-commit
A setup for Husky pre-commit checks in a JavaScript or TypeScript repository. A pre-commit hook runs automatically before a Git commit and can format staged files, check types, and run tests.
ratchet-files
Ratchet source file size so every file stays small enough for an agent to read whole: find every file over a token budget, split oversized files by concept, and set up the pre-commit ratchet that stops them from growing. Use when a commit is blocked because a file is over the size budget, when asked to find or split…
push-all
Use when the user explicitly asks to stage all current changes, create a commit, and push to the remote after safety checks.
review-gate
Use before an agent-produced diff is committed, pushed, opened as a PR, merged, landed, or applied to user files when explicit implementation approval is missing. Trigger for review gate, review pack, approve before landing, diff first then land, human approval, merge gate, commit gate, push gate, or PR readiness.…
at-daily-log
Summarize each day's Git activity into a concise daily work log, for a single date or a range. Uses the current repository, optional configured work projects, or paths named in conversation; configuration is never required.
checkpoint-management
Git-backed state management for safe rollback. Create and restore checkpoints with tagged commits and metadata tracking.