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 aretw0/agents-lab --skill commitgit clone --depth 1 https://github.com/aretw0/agents-labWrote 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/aretw0/agents-lab/commit)<a href="https://agentmods.dev/skills/aretw0/agents-lab/commit"><img src="https://agentmods.dev/badge/skills/aretw0/agents-lab/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/aretw0/agents-lab/commit"><img src="https://agentmods.dev/badge/skills/aretw0/agents-lab/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.00009 | $0.00411 |
| Opus 5.5 | $0.00004 | $0.00164 |
| Sonnet 5.5 | $0.00002 | $0.00082 |
| Haiku 4.5 | $0.00001 | $0.00041 |
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
Create a git commit for the current changes using a concise Conventional Commits-style subject.
Format
<type>(<scope>): <summary>
typeREQUIRED. Usefeatfor new features,fixfor bug fixes. Other types:docs,refactor,chore,test,perf,style,ci.scopeOPTIONAL. Short noun in parentheses for the affected area (e.g.,api,auth,ui,cli).summaryREQUIRED. Short, imperative, lowercase, ≤ 72 chars, no trailing period.
Rules
- Body is OPTIONAL. If needed, add a blank line after the subject and write short paragraphs.
- Do NOT include breaking-change markers or footers.
- Do NOT add sign-offs (
Signed-off-by). - Only commit — do NOT push.
- Always pass the message on the command line, never rely on an interactive editor:
git commit -m "fix(auth): handle expired token on refresh" - If it is unclear which files to include, ask before staging.
- Treat caller-provided arguments as additional commit guidance:
- Freeform text → influences scope, summary, and body
- File paths/globs → limit which files to stage and commit
- Combined → honor both
Steps
- Check if the user provided specific file paths/globs and/or instructions.
- Run
git statusandgit diffto understand current changes. - (Optional) Run
git log -n 20 --pretty=format:%sto see commonly used scopes in this project. - Ask for clarification if there are ambiguous extra files.
- Stage only the intended files.
- Run
git commit -m "<subject>"(add-m "<body>"if a body is 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.
- 1mo ago First seen · 40 lines · 9 tokens per session scan A 4494e711830a
commit is a skill published in the GitHub repository aretw0/agents-lab (11 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 411 once invoked, about $0.0000 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
speckit-checkpoint-commit
Commit changes at meaningful checkpoints throughout the workflow.
gaia-badge-provision
Procedure for controlled, human-gated outbound README badge provisioning PRs (Issue #1817). Preflights upstream repositories, ensures single-badge placement with deep links, and records campaign outcomes without automated retries or multi-badge noise.
pr
Push committed changes and create a draft PR on GitHub. Use when you have staged changes ready to push and want to open a draft PR for early feedback or documentation.
fp-implement
Implement a scoped feature-pipeline plan in coherent commits and push each meaningful unit. Use for "implement the plan", "apply the plan", or the implementation stage; routine lean/economy work does not require planApproved, while explicit human gates remain binding.
regen
Manually trigger artifact regeneration, versioning, and chore commit. Use when you need fine-grained control over when registry artifacts sync (outside the automated sync-artifacts.yml workflow).
speckit-taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.