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/aretw0/agents-lab/commitnpx skills add aretw0/agents-lab --skill commitgit clone --depth 1 https://github.com/aretw0/agents-labWhat 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.00009 | $0.00411 |
| Opus 5 | $0.00005 | $0.00205 |
| Sonnet 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 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
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.
- yesterday 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 2mo ago), licensed MIT. It adds 9 tokens to every session and 411 once invoked, about $0.0000 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
agentbro-release
Use when releasing AgentBro from this repository: merging dev/main, bumping versions, updating release notes, tagging, pushing, monitoring GitHub Actions, Homebrew cask publication, or fixing a bad release.
agentbro-pr-merge
Use when reviewing, fixing CI for, approving workflows for, or merging AgentBro pull requests into dev/main, especially external contributor PRs where contributor attribution matters.
source-command-check
跑全套本地校验(前端 lint/test/build + Rust check)。.
gpt-control
Use when the user asks to get an independent ChatGPT web review, continue a GPT-Control conversation, inspect a model run, or generate or iterate on an image through a configured browser driver. Not for facts the working tree or a local test can answer directly.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.