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/evmts/guillotine-mini/commitgit clone --depth 1 https://github.com/evmts/guillotine-miniWhat 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.00011 | $0.01079 |
| Opus 5 | $0.00005 | $0.00540 |
| Sonnet 5 | $0.00002 | $0.00216 |
| Haiku 4.5 | $0.00001 | $0.00108 |
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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intelligent Git Commit Command
Analyze the current git repository state and create atomic, conventional commits with emoji prefixes. Automatically filter out temporary/debug files and group related changes logically.
Instructions
-
Analyze Repository State
- Run
git status --porcelainto see all changes - Run
git diff --cachedto see staged changes - Run
git diffto see unstaged changes - Show a summary of what files have changed
- Run
-
Filter Temporary Files Unless
--allis specified in $ARGUMENTS, automatically exclude these patterns:- Files starting with
test_,debug_,temp_ - Files ending with
.tmp,.log,.bak,.swp,.swo,~ - IDE directories:
.vscode/,.idea/,.vs/ - Build artifacts:
node_modules/,target/debug/,target/release/,.zig-cache/,zig-out/ - OS files:
.DS_Store,Thumbs.db - Submodules: NEVER commit, clean, or modify any files within git submodules (e.g.,
execution-specs/)
Explain what files were filtered out and why.
- Files starting with
-
Group Changes Logically Group files into logical atomic commits based on:
- EVM module:
src/evm/files - Core functionality:
src/files (non-EVM) - Tests:
test/files or files containing "test" - Documentation:
.mdfiles ordoc/files - Build system:
build.zig, build-related files - Benchmarks:
bench/files - Claude Code:
.claude/,CLAUDE.mdfiles - Miscellaneous: Everything else
- EVM module:
-
Determine Commit Types For each group, analyze and determine the appropriate conventional commit type:
- 🎉 feat: New features or functionality
- 🐛 fix: Bug fixes
- ♻️ refactor: Code refactoring without functional changes
- 📚 docs: Documentation updates
- ✅ test: Adding or updating tests
- 🔧 chore: Maintenance tasks, dependency updates
- 🎨 style: Code style/formatting changes
- ⚡ perf: Performance improvements
- 🔨 build: Build system changes
- 👷 ci: CI/CD changes
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 · 109 lines · 0 tokens per session scan A 22503decb4a6
commit is a command published in the GitHub repository evmts/guillotine-mini (10 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 1,079 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.