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 knowns-dev/knowns --skill kn-commitgit clone --depth 1 https://github.com/knowns-dev/knownsWrote 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/knowns-dev/knowns/kn-commit)<a href="https://agentmods.dev/skills/knowns-dev/knowns/kn-commit"><img src="https://agentmods.dev/badge/skills/knowns-dev/knowns/kn-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/knowns-dev/knowns/kn-commit"><img src="https://agentmods.dev/badge/skills/knowns-dev/knowns/kn-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.00016 | $0.00727 |
| Opus 5.5 | $0.00006 | $0.00291 |
| Sonnet 5.5 | $0.00003 | $0.00145 |
| Haiku 4.5 | $0.00002 | $0.00073 |
Grade A, and why
kn-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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Committing Changes
Announce: "Using kn-commit to commit changes."
Core principle: VERIFY BEFORE COMMITTING - check staged changes, ask for confirmation.
Inputs
- Current staged changes
- Relevant task IDs, scope, and reason for the change
Preflight
- Confirm the correct files are staged
- Check whether the commit should reference a task or feature area
- Refuse to commit if the staged diff looks unrelated or mixed across multiple concerns
Step 1: Review Staged Changes
git status
git diff --staged
Step 2: Generate Commit Message
Format:
<type>(<scope>): <message>
- Bullet point summarizing change
Types: feat, fix, docs, style, refactor, perf, test, chore
Rules:
- Title lowercase, no period, max 50 chars
- Body explains why, not just what
Step 3: Ask for Confirmation
Ready to commit:
feat(auth): add JWT token refresh
- Added refresh token endpoint
Proceed? (yes/no/edit)
Wait for user approval.
Step 4: Commit
git commit -m "feat(auth): add JWT token refresh
- Added refresh token endpoint"
Final Response Contract
All built-in skills in scope must end with the same user-facing information order: kn-init, kn-spec, kn-flow, kn-go, kn-plan, kn-research, kn-handoff, kn-implement, kn-test, kn-review, kn-debug, kn-decision, kn-verify, kn-doc, kn-template, kn-extract, and kn-commit.
Required order for the final user-facing response:
- Goal/result - state whether a commit was proposed, blocked, or created.
- Key details - include the proposed or final commit message, relevant diff concerns, and approval status.
- Next action - recommend a concrete follow-up command only when a natural handoff exists.
Keep this concise for CLI use. Skill-specific content may extend the key-details section, but must not replace or reorder the shared structure.
Do not manage platform-synced skill copies; this source defines the built-in workflow contract.
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 · 115 lines · 16 tokens per session scan A b91dffcf7eac
kn-commit is a skill published in the GitHub repository knowns-dev/knowns (249 stars, last pushed 18d ago), licensed MIT. It adds 16 tokens to every session and 727 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
committing
Creates quality git commits with conventional commit format. Use when asked to commit changes or create a commit message.
sc-diff-report
Incremental security scan for changed files only — optimized for PR and commit-level reviews.
commit-conventions
Enforces conventional commit format with atomic changes and co-author attribution. Used when committing code changes to maintain consistent git history.
tdd
Enforces red-green-refactor TDD cycle with atomic commits per phase. Used when implementing features, fixing bugs, or when tests should drive the design.
cw-land
Use when turning verified Codewhale work into commits, branches, or a merge: choosing direct-main vs. worktree vs. integration branch, preserving contributor credit, and honoring the gate artifact before merging.
git-master
Handles git work: atomic commits, rebase, squash, blame, bisect, reflog, and history questions. Use whenever a task needs a commit or a git-history investigation; skip for ordinary code edits.