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/wittyreference/twilio-claude-plugin/commitgit clone --depth 1 https://github.com/wittyreference/twilio-claude-pluginWhat 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.00020 | $0.00569 |
| Opus 5 | $0.00010 | $0.00284 |
| Sonnet 5 | $0.00004 | $0.00114 |
| Haiku 4.5 | $0.00002 | $0.00057 |
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 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.
What it actually says
Commit Helper
Stage and commit changes with pre-commit validation and conventional commit messages.
Pre-Commit Checks
Run these checks before staging. Stop and report if any fail.
1. TypeScript Compilation (if applicable)
If a tsconfig.json exists in the project or any modified files are TypeScript:
npx tsc --noEmit
2. Test Suite
npm test --bail
3. ABOUTME Comments
For any new files (untracked), verify they start with a 2-line ABOUTME comment:
// ABOUTME: [What this file does]
// ABOUTME: [Key behaviors or context]
Flag any missing ones -- do not commit without them.
Staging
Prefer staging specific files over git add -A:
git add <file1> <file2> ...
Review the diff of what will be committed:
git diff --cached
Do NOT stage files that likely contain secrets (.env, credentials.json, etc.).
Commit Message
Generate a conventional commit message from the staged diff.
Format
Use HEREDOC format. NEVER use --no-verify.
git commit -m "$(cat <<'EOF'
<type>: <description in imperative mood>
- Detail 1
- Detail 2
Co-Authored-By: Claude <[email protected]>
EOF
)"
Types
| Type | When |
|---|---|
feat |
New feature or capability |
fix |
Bug fix |
test |
Adding or updating tests |
refactor |
Code restructuring without behavior change |
docs |
Documentation only |
Post-Commit
1. Todo Check
If a todo.md file exists in the project root, and the committed work completes a todo item, check it off.
2. Pending Actions
If a .claude/pending-actions.json file exists, mention any doc update suggestions related to the committed files.
Output
## Commit Complete
SHA: <short sha>
Message: <commit message first line>
Files: <count> files changed
Post-commit:
- Todo: <updated / no changes>
- Pending actions: <suggestions found / none>
What to Commit
<user_request> $ARGUMENTS </user_request>
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 · 114 lines · 20 tokens per session scan A 9334f825749e
commit is a command published in the GitHub repository wittyreference/twilio-claude-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 569 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.