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 mochow13/keen-code --skill commitgit clone --depth 1 https://github.com/mochow13/keen-codeWrote 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/mochow13/keen-code/commit)<a href="https://agentmods.dev/skills/mochow13/keen-code/commit"><img src="https://agentmods.dev/badge/skills/mochow13/keen-code/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/mochow13/keen-code/commit"><img src="https://agentmods.dev/badge/skills/mochow13/keen-code/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.00022 | $0.00465 |
| Opus 5.5 | $0.00009 | $0.00186 |
| Sonnet 5.5 | $0.00004 | $0.00093 |
| Haiku 4.5 | $0.00002 | $0.00047 |
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 Skill
User intent (optional): $ARGUMENTS
Steps
-
Survey the working tree. Run in parallel:
git status --shortgit diff --stagedgit diffgit log -n 5 --oneline
Use the log to learn the repo's commit-message style (conventional commits, plain sentences, scope prefixes, etc.).
-
Decide what to stage.
- Stage tracked changes the user clearly intends to commit. Name files explicitly with
git add <path>. - If there are untracked files, list them to the user and ask which (if any) should be included. Do not stage them silently.
- Do not use
git add -Aorgit add .— they can leak secrets or stray files.
- Stage tracked changes the user clearly intends to commit. Name files explicitly with
-
Draft the message.
- Lead with why over what. The diff already shows the what.
- Match the recent
git logstyle. - Subject line under ~72 characters. If a body is needed, separate with a blank line.
- If the user provided intent in the line above, weave it in — do not quote it verbatim.
- Do not add co-author or "generated with" trailers unless the user explicitly asks.
-
Commit. Use a heredoc so multi-line bodies survive shell quoting:
git commit -m "$(cat <<'EOF' <subject> <optional body> EOF )" -
Verify. Run
git statusand report the result to the user. Do not push — that is a separate, explicit step the user must request.
On hook failures
If a pre-commit hook fails, do not retry with --no-verify. Read the hook output, fix the underlying issue, re-stage the affected files, and create a new commit. Never amend in this case — the prior commit did not happen, so --amend would target the wrong thing.
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 · 51 lines · 22 tokens per session scan A ede46a503a4e
commit is a skill published in the GitHub repository mochow13/keen-code (72 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 465 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
yeet
Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with gh used only as a fallback where connector coverage is insufficient.
github
Use the gh CLI for GitHub issues, PR status, CI/logs, comments, reviews, releases, and API queries.
git-commit
Create well-structured git commits using the Conventional Commits specification. Use when asked to "commit changes", "create a git commit", "stage and commit", "write a commit message", or "/commit". Analyzes diffs to auto-detect type and scope, generates semantic commit messages, and supports intelligent file staging.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.