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/lee-w/maigo/commitizen-awarenpx skills add Lee-W/maigo --skill commitizen-awaregit clone --depth 1 https://github.com/Lee-W/maigoWhat 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.00096 | $0.01826 |
| Opus 5 | $0.00048 | $0.00913 |
| Sonnet 5 | $0.00019 | $0.00365 |
| Haiku 4.5 | $0.00010 | $0.00183 |
Grade A, and why
commitizen-aware 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.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commitizen-Aware
Loaded by: repo-detect hook (SessionStart) when commitizen-tools/commitizen is detected in git remote or file structure.
Applies to: Any skill execution within a commitizen-tools/commitizen contributor checkout — review, quick-fix, refactoring, or otherwise.
When to apply
This is a knowledge layer, not a review checklist.
It is loaded automatically by the
repo_detect hook
at session start when a commitizen repo is detected.
It mirrors and supplements the repo's own AGENTS.md, condensed for agent context.
It can also be triggered manually via a memory entry with triggers: [commitizen-aware]
(see Memory-triggered skill loading).
Once loaded, treat every convention as background — do not re-read each task.
Read AGENTS.md first
The single source of truth for contributor conventions lives in the repo itself.
- First action: read
AGENTS.md(83 lines — short enough to read in full). - Conflict resolution: if anything in this skill contradicts
AGENTS.md, the repo file wins. This skill is an onramp and supplement, not a competing authority. - PR-specific guidance: when working on a pull request, also read
docs/contributing/pull_request.mdand.github/pull_request_template.md(both explicitly named in AGENTS.md line 25).
Contributor conventions
1. Defer to AGENTS.md
This skill is an onramp — a condensed version of AGENTS.md formatted for agent startup context.
It is not a replacement. Any time a convention here conflicts with what AGENTS.md says,
follow AGENTS.md. See the Read AGENTS.md first section above.
2. Environment — uv + prek + poe
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 · 147 lines · 96 tokens per session scan A 48ed6362cea4
commitizen-aware is a skill published in the GitHub repository Lee-W/maigo (14 stars, last pushed 8d ago), licensed MIT. It adds 96 tokens to every session and 1,826 once invoked, about $0.0005 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…