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/edonadei/caliper/commit-simplenpx skills add edonadei/caliper --skill commit-simplegit clone --depth 1 https://github.com/edonadei/caliperWhat 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.00020 | $0.00313 |
| Opus 5 | $0.00010 | $0.00156 |
| Sonnet 5 | $0.00004 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
commit-simple 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 2d 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
Use this skill when creating a branch, committing changes, or pushing work.
Workflow
- Inspect the current branch, working tree, staged changes, and diff.
- Propose any branch change, commit split, and Conventional Commit message(s).
- After confirmation, create the branch if needed and commit.
- Offer to push after the commit.
- If the user wants a pull request, suggest
commit-pras the next step.
Rules
- If there are logically separate changes, propose separate commits and confirm the plan before committing.
- If the current branch is
mainormaster, ask whether to create a new branch before committing. - For new branches, use
{type}/sc-{number}/{slug},{type}/gh-{number}/{slug},{type}/{number}/{slug}, or{type}/{slug}. - When working inside a ticket worktree folder, keep the branch aligned with the folder's ticket id.
- Use Conventional Commits for commit messages.
- Commit messages should describe the resulting code change, not the development process.
- Unless the change is trivial, include a concise human-readable body that explains why the change matters and any important reviewer context.
- Prefer concrete facts over workflow labels: name the behavior, API, module, or cleanup that changed.
- Ask before committing or pushing.
- Hand pull request work off to
commit-pr.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 30 lines · 20 tokens per session scan A f27c75d902b1
commit-simple is a skill published in the GitHub repository edonadei/caliper (50 stars, last pushed 2d ago), licensed MIT. It adds 20 tokens to every session and 313 once invoked, about $0.0001 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
demo-reviewer
Demo skill for the Skill Eval Harness example. Use it to review a proposed change and label the severity of each finding.
agent-eval-skills
Evaluate an existing agent skill with Promptfoo-native behavior, routing, or role-play tests. Use when a skill needs executable evidence that its product promise works. Do not use to author the domain skill itself.
setup-skills-evals
Set up the skills-evals library in a repository — discover agent artifacts, interview the user about what to test, scaffold eval cases, and wire CI and local runners. Use when the user wants to set up skills-evals, test their agent skills, add evals for skills or custom agents, check why a skill isn't triggering, or…
bugfix-workflow
Use when the user reports a concrete bug in an existing application and asks for a code fix. Reproduce the bug, write or run a verifier that fails, change the smallest amount of code that makes the verifier pass, re-run the verifier, and explain the change. Do not use for: feature requests, code review, dependency…
test-driven-development
Write a failing test before implementing any fix or feature. Use when fixing bugs, adding features, or refactoring code that lacks test coverage.
commit-messages
Draft clear conventional commit messages. Use when committing changes, drafting a commit message, or reviewing git history hygiene.