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 aidyou/chatspeed --skill commitgit clone --depth 1 https://github.com/aidyou/chatspeedWrote 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/aidyou/chatspeed/commit)<a href="https://agentmods.dev/skills/aidyou/chatspeed/commit"><img src="https://agentmods.dev/badge/skills/aidyou/chatspeed/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/aidyou/chatspeed/commit"><img src="https://agentmods.dev/badge/skills/aidyou/chatspeed/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00025 | $0.00427 |
| Opus 5.5 | $0.00010 | $0.00171 |
| Sonnet 5.5 | $0.00005 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00043 |
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
Commit
Create a local Git commit with real Git commands and a Conventional Commit message.
Workflow
- Inspect Git status, staged files, recent commits, and the relevant diff.
- Keep unrelated changes out of the commit. Ask before including unclear changes or splitting commits.
- Check candidate paths and diffs for sensitive data.
- Run checks only when the user explicitly requests them.
- Stage the intended files and create the commit.
- Report the commit and any checks that actually ran.
Optional Verification
Do not run lint, tests, builds, typechecks, or documentation generation just because the user asked for a commit. A local commit is not a push or CI gate.
Run a check only when the user explicitly requests testing or verification. Use the narrowest relevant existing project command.
Staging Rules
If files are already staged, commit only those files unless instructed otherwise. Otherwise, stage only files belonging to the requested change. Never discard, reset, clean, or overwrite existing changes.
Commit Message
Match the recent repository style and language. Use:
<type>[optional scope]: <concise description>
Keep the subject under 72 characters and state the key change. Add a short body only when it is needed to explain an important behavior change, compatibility impact, or breaking change. Do not add exhaustive implementation detail.
Sensitive Data Review
Before staging, inspect candidate files and diffs for secrets, credentials, private keys, tokens, connection strings, local databases, or data exports. If a possible secret is found, stop and ask the user whether to exclude or explicitly include each affected file.
Safety
- Use real Git commands; do not call a nonexistent custom commit command.
- Do not create branches, stashes, resets, checkouts, cleanups, or pushes without explicit approval.
- Create a commit only when the user explicitly asks for one.
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 · 50 lines · 25 tokens per session scan A 70db4232f9f6
commit is a skill published in the GitHub repository aidyou/chatspeed (21 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 427 once invoked, about $0.0001 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
commit-messages
Write git commit messages and pull request titles in the WARP format used by the swarms repo.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
setup-pre-commit
A setup guide for Git pre-commit checks, which run automatically before a commit is created. It configures Husky, lint-staged, Prettier, type checking, and tests in a repository.
commit-and-push
Create a well-formatted git commit and push to remote repository.
customize-contribute-back
Contribute a user's AIWG customization back upstream as a PR — reviews for general applicability, creates branch, opens PR.
effect-ledger
Record an effect, sign an effect, reconcile an effect or check "did this PR merge" through the signed AIWG effect ledger, using one aiwg effect command with scriptable exit codes.