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 skills/grehnen/copilot-tooling/gitmojinpx skills add grehnen/copilot-tooling --skill gitmojigit clone --depth 1 https://github.com/grehnen/copilot-toolingWhat 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.00035 | $0.00261 |
| Opus 5 | $0.00017 | $0.00130 |
| Sonnet 5 | $0.00007 | $0.00052 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
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 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
Gitmoji Commit Messages
Always generate exactly one commit message — never a list, never one per file.
Summarize all changes together in one subject line. Prefix it with the most SPECIFIC emoji that represents the overall change.
Format: <emoji> <imperative summary> (≤72 chars). Only write a body if deemed absolutely necessary. Use the emoji character, not the :code:.
Emoji definitions: ./references/gitmojis.md
Output the commit message in markdown format inside a code block.
Shortcommands
When the skill is invoked with one of the shortcommands below, follow the instructions for that command.
/gitmojior/gitmoji staged: write a commit message for all staged changes./gitmoji chat: write a commit message for changes from this chat session./gitmoji all: suggest a commit message for all staged and unstaged changes./gitmoji split: help the user split all the current changes into multiple distinct commits.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 26 lines · 35 tokens per session scan A c0a72542626d
gitmoji is a skill published in the GitHub repository grehnen/copilot-tooling (2 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 261 once invoked, about $0.0002 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 skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
commits
Use this skill whenever the user asks to commit changes, write or fix a commit message, amend or rename a commit, or do a workflow that includes committing in the IntelliJ repository. This is a thin repo-specific overlay: use IntelliJ commit format, write full commit messages by default, and keep requested suffixes…
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…