Borrowing it
Nothing to install: this file belongs to evmts/tevm. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/evmts/tevm/main/.claude/commands/add-gitmoji.mdgit clone --depth 1 https://github.com/evmts/tevmWrote 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/commands/evmts/tevm/add-gitmoji)<a href="https://agentmods.dev/commands/evmts/tevm/add-gitmoji"><img src="https://agentmods.dev/badge/commands/evmts/tevm/add-gitmoji/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/commands/evmts/tevm/add-gitmoji"><img src="https://agentmods.dev/badge/commands/evmts/tevm/add-gitmoji.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.00306 |
| Opus 5.5 | $0.00000 | $0.00122 |
| Sonnet 5.5 | $0.00000 | $0.00061 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
add-gitmoji 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.
What it actually says
Add Gitmoji Hook
This command will install gitmoji in the current worktree by:
- Creating the hooks directory if needed
- Setting up the prepare-commit-msg hook for gitmoji
- Making the hook executable
The gitmoji hook allows you to select emoji for your commits using an interactive prompt.
Do you want to proceed with installing the gitmoji commit hook?
#!/usr/bin/env bash
# Get .git directory for current worktree
GIT_DIR=$(git rev-parse --git-dir)
echo "Installing gitmoji hook to $GIT_DIR/hooks..."
# Create hooks directory if it doesn't exist
mkdir -p "$GIT_DIR/hooks"
# Create the prepare-commit-msg hook file
cat > "$GIT_DIR/hooks/prepare-commit-msg" << 'EOF'
#!/usr/bin/env bash
# gitmoji as a commit hook
if npx -v >&/dev/null
then
exec < /dev/tty
npx -c "gitmoji --hook $1 $2"
else
exec < /dev/tty
gitmoji --hook $1 $2
fi
EOF
# Make sure the hook is executable
chmod +x "$GIT_DIR/hooks/prepare-commit-msg"
echo "✅ Gitmoji hook installed successfully!"
echo "You can now use gitmoji in your commits with: npx gitmoji-cli -c"
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 · 41 lines · 0 tokens per session scan A 979eeff619e2
add-gitmoji is a command published in the GitHub repository evmts/tevm (449 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 306 tokens. 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
speckit.companion.living-sync
Sync living specs from your current changes — group working-tree changes (uncommitted included) by capability and update every affected spec in one pass (opt-in, update-not-regenerate, never halts).
push-changes
If no topic provided, just document the recent changes. If a topic is provided, focus on documenting that topic.
sync-tutorials
Commit and push your tutorials to the GitHub repository for backup and mobile reading.
git-commit
Based on the above changes, create a single git commit. Use the Angular commit message format：.
commit-push-pr
Commit, push, and open a PR (includes changeset creation).
commit
Based on the above changes, create a single git commit.