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 rules/zackiles/deno-kit/create-commit-messagegit clone --depth 1 https://github.com/zackiles/deno-kitWhat 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.00008 | $0.00492 |
| Opus 5 | $0.00004 | $0.00246 |
| Sonnet 5 | $0.00002 | $0.00098 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
create-commit-message 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 yesterday.
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.
This is a copy
100% identical to create-commit-message — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Writing Commit Messages With Convention Commit
You must format commit messages using the Conventional Commits standard.
Only apply this rule when generating or suggesting commit messages.
Format:
<type>(<scope>): <description>
- Type: Defines the nature of the change.
- Scope: Derived from the file path or affected component.
- Description: Written in imperative mood.
Types:
- feat: A new feature.
- fix: A bug fix.
- docs: Documentation changes only.
- style: Code formatting, no logic change.
- refactor: Code restructuring, no behavior change.
- perf: Performance improvements.
- test: Adding or improving tests.
- chore: Build process, dependencies, or auxiliary tools.
Commit Logic
function generateCommitMessage(file, changeDescription) {
let changeType = "chore"
if (/add|create|implement/i.test(changeDescription)) changeType = "feat"
else if (/fix|correct|resolve/i.test(changeDescription)) changeType = "fix"
else if (/refactor|restructure/i.test(changeDescription)) changeType = "refactor"
else if (/test/i.test(changeDescription)) changeType = "test"
else if (/doc|comment/i.test(changeDescription)) changeType = "docs"
else if (/style|format/i.test(changeDescription)) changeType = "style"
else if (/perf|optimize/i.test(changeDescription)) changeType = "perf"
const scope = file.split("/").slice(0, -1).join("-")
return `${changeType}(${scope}): ${changeDescription}`
}
Conventional Commit Examples
Input 1:
CHANGE_DESCRIPTION="add user authentication function"
FILE="src/auth/login.ts"
Output 1:
feat(src-auth): add user authentication function
Input 2:
CHANGE_DESCRIPTION="fix incorrect date parsing"
FILE="lib/utils/date.js"
Output 2:
fix(lib-utils): fix incorrect date parsing
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.
- yesterday First seen · 72 lines · 8 tokens per session scan A 26bc840cf851
create-commit-message is a cursor rule published in the GitHub repository zackiles/deno-kit (3 stars, last pushed 5mo ago), licensed MIT. It adds 8 tokens to every session and 492 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to create-commit-message, differing in 8 lines, and is treated as a copy.
Other cursor rules, from other repositories
development-conventions
Development conventions, code style, and best practices for the Kaneo project.
docs
This file provides guidelines for working with the documentation in the /docs directory.
architecture
Architecture of openapi-to-cli (ocli).
architecture-constraints
GolemBot architecture hard constraints — must check before modifying any src/ code.
app_feature_first_architecture
Feature-first architecture is a design pattern that organizes code by business features rather than technical layers. This approach promotes better maintainability, scalability, and team collaboration by keeping related functionality together and reducing coupling between different parts of the application.
best_practices
Advanced Best Practices covering Error Handling, Environment Variables, Performance, and Accessibility rules.