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 commands/caretive-ai/project-careti/commitgit clone --depth 1 https://github.com/caretive-ai/project-caretiWhat 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.00010 | $0.00192 |
| Opus 5 | $0.00005 | $0.00096 |
| Sonnet 5 | $0.00002 | $0.00038 |
| Haiku 4.5 | $0.00001 | $0.00019 |
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 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 Command
Create a git commit following project conventions.
Workflow
- Run
git statusto see changes - Run
git diff --stagedto review staged changes - If no staged changes, ask user what to stage
- Generate commit message following conventional commits format
- Create commit with generated message
Commit Message Format
<type>(<scope>): <subject>
<body>
<footer>
Types
- feat: New feature
- fix: Bug fix
- docs: Documentation only
- style: Formatting, no code change
- refactor: Code restructuring
- test: Adding tests
- chore: Maintenance tasks
Notes
- Always use conventional commits format
- Include scope when relevant
- Keep subject line under 72 characters
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 · 39 lines · 10 tokens per session scan A 24466245406a
commit is a command published in the GitHub repository caretive-ai/project-careti (47 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 10 tokens to every session and 192 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 commands, from other repositories
port-commits
把已落地、可追溯的一组 commit，用 cherry-pick（最稳妥） 同步到目标分支（常见：main → hc-0730）。.
checkpoint
Create a git checkpoint to safely save current progress.
vouch-propose-from-pr
Distill a merged PR into vouch claim proposals.
git-commit
Create a git commit for the current changes using Conventional Commits-style format.
commit
Создать git commit с правильным сообщением.
commit-and-pr
Let's commit the changes. Run tests, typechecks, and format checks. Then commit, push, and create a pull request.