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/bdiasti/maestro-bundle-cli/commit-patternnpx skills add bdiasti/maestro-bundle-cli --skill commit-patterngit clone --depth 1 https://github.com/bdiasti/maestro-bundle-cliWhat 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.00029 | $0.00886 |
| Opus 5 | $0.00015 | $0.00443 |
| Sonnet 5 | $0.00006 | $0.00177 |
| Haiku 4.5 | $0.00003 | $0.00089 |
Grade A, and why
commit-pattern 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Pattern
Generate structured commit messages following Conventional Commits and the organization's standards.
When to Use
- When committing code changes
- When asked to generate a commit message
- When finishing a task and need to commit the result
- When reviewing commit messages for compliance
Available Operations
- Generate a commit message from staged changes
- Validate an existing commit message
- Create a multi-line commit with body and footer
- Stage and commit changes in one workflow
Multi-Step Workflow
Step 1: Review Staged Changes
Inspect what has been changed to determine the appropriate commit type and scope.
git status
git diff --cached --stat
git diff --cached
Step 2: Determine Commit Type
| Type | When to use |
|---|---|
feat |
New user-facing functionality |
fix |
Bug fix |
refactor |
Code change that does not alter behavior |
docs |
Documentation-only changes |
test |
Adding or fixing tests |
chore |
Build, deps, configs, maintenance tasks |
ci |
CI/CD changes (pipelines, workflows) |
perf |
Performance improvement |
Step 3: Compose the Message
Follow the format:
<type>(<scope>): <imperative description in Portuguese>
Rules:
- Imperative mood: "adicionar", not "adicionado" or "adicionando"
- First letter lowercase
- No period at the end
- Maximum 72 characters on the first line
- Scope is the affected module/feature
- If the change breaks compatibility, add
BREAKING CHANGE:in the body
Step 4: Commit
# Simple commit
git commit -m "feat(demands): adicionar decomposicao automatica de tasks"
# Commit with body for complex changes
git commit -m "refactor(orchestrator): simplificar alocacao de agentes
A alocacao anterior usava um loop O(n^2) comparando todos os agentes
com todas as tasks. Agora usa um mapa indexado por tipo de agente,
reduzindo para O(n)."
Step 5: Verify
git log --oneline -1
Resources
references/conventional-commits.md- Full Conventional Commits specification and examples
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 · 118 lines · 29 tokens per session scan A ea1c6886b4fe
commit-pattern is a skill published in the GitHub repository bdiasti/maestro-bundle-cli (21 stars, last pushed 5mo ago), licensed MIT. It adds 29 tokens to every session and 886 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-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…