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 ronronner02/codepilot-agent --skill spec-commitgit clone --depth 1 https://github.com/ronronner02/codepilot-agentWrote 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/ronronner02/codepilot-agent/spec-commit)<a href="https://agentmods.dev/skills/ronronner02/codepilot-agent/spec-commit"><img src="https://agentmods.dev/badge/skills/ronronner02/codepilot-agent/spec-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/ronronner02/codepilot-agent/spec-commit"><img src="https://agentmods.dev/badge/skills/ronronner02/codepilot-agent/spec-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.00032 | $0.01606 |
| Opus 5.5 | $0.00013 | $0.00642 |
| Sonnet 5.5 | $0.00006 | $0.00321 |
| Haiku 4.5 | $0.00003 | $0.00161 |
Grade A, and why
spec-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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit
Create a single, well-crafted git commit from the current working tree changes.
Invocation And Authorization Boundary
This is an internal-only helper. A public workflow may delegate here only after the current user or a visible upstream handoff has established commit_authorization: authorized for the intended run-owned paths. workflow invocation does not authorize commit; tool permission, a dirty tree, a branch name, or successful verification are execution facts, not authority. When commit authorization is missing, stop before branch mutation, staging, or commit and return commit_authorization_missing.
This helper owns commit composition and the authorized commit checkpoint only. It does not own push, PR creation/update, plan lifecycle, or unrelated dirty paths. If branch creation would be required, obtain explicit approval for that concrete branch mutation before creating it.
Context
Gather Git context by running each command as its own argv-style shell tool call. Do not join commands with shell separators, pipes, substitutions, or redirects; those forms are host-shell-specific and can hide the real exit status.
| Command | Purpose | Non-zero or empty result |
|---|---|---|
git status |
Working-tree state | Not a Git repository: stop |
git diff HEAD |
Uncommitted changes | An unborn repo may have no HEAD; inspect tracked changes directly |
git branch --show-current |
Current branch | Empty output means detached HEAD |
git log --oneline -10 |
Commit-message convention | An unborn repo has no history |
git rev-parse --abbrev-ref origin/HEAD |
Remote default branch | Resolve it using the fallback in Step 1 |
These facts are a snapshot. Re-read the branch and staged paths immediately before committing because the working tree may change after intake.
Workflow
Step 1: Gather context
Run every command in the Context section as a separate shell tool call.
The remote default branch value returns something like origin/main. Strip the origin/ prefix to get the branch name. If the command exited non-zero or returned a bare HEAD, try:
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 · 113 lines · 32 tokens per session scan A debaaaa92095
spec-commit is a skill published in the GitHub repository ronronner02/codepilot-agent (0 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 1,606 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-31.
Other skills, from other repositories
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
release-sync
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.
artifact-metadata
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle.
customize-setup
Set up personal AIWG customization mode from a local clone or fork — makes your clone the live global AIWG instance so edits go live immediately.
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.
customize-contribute-back
Contribute a user's AIWG customization back upstream as a PR — reviews for general applicability, creates branch, opens PR.