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/quatico-solutions/agent-skills/commit-notationnpx skills add quatico-solutions/agent-skills --skill commit-notationgit clone --depth 1 https://github.com/quatico-solutions/agent-skillsWhat 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.00073 | $0.01024 |
| Opus 5 | $0.00036 | $0.00512 |
| Sonnet 5 | $0.00015 | $0.00205 |
| Haiku 4.5 | $0.00007 | $0.00102 |
Grade A, and why
commit-notation 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Notation
Source of truth: QuaticoCommitNotation (GitHub) SYNC REQUIRED: Changes here MUST stay consistent with the canonical repo. Changes incomplete without sync.
Quatico uses Arlo's Commit Notation v1 with extensions (T, E).
Quick Reference
| Risk Level | Format | Example |
|---|---|---|
| Known Safe | x |
r Extract method getData |
| Validated | X |
R: Extract method getData |
| Risky | X!! |
R!! Rename across files |
| Broken | X** |
F** WIP: new feature |
Intentions
Core
| Letter | Name | Use When |
|---|---|---|
| F | Feature | Adding or changing behavior |
| B | Bugfix | Fixing broken behavior |
| R | Refactoring | Changing implementation, not behavior |
| D | Documentation | Non-code documentation changes |
Extensions
| Letter | Name | Use When |
|---|---|---|
| T | Test-only | Alter tests without altering functionality |
| E | Environment | Dev setup, tooling, non-code changes |
| WIP | Unknown | Mixed changes, just checking in |
Risk Level Guidelines
Known Safe (lowercase): Provable correctness - tool-verified refactoring, type-checked renames. Validated (UPPERCASE): Test-verified - ran tests, all pass. Risky (XX!!): Attempted but not fully verified. Broken (XX)**: WIP, may not compile, no verification.
Commit Message Format
X: Summary in active voice
TICKET-123
Rules:
- Separator:
:or nothing (e.g.,F: Add featureorF Add feature) - Voice: Active ("Add feature") not progressive ("Adding feature")
- Length: Subject < 75 chars
- Ticket: Last line, blank line before, NO
#prefix (git treats#as comment)
Writing Commit Messages
- Determine intention: F, B, R, D, T, E, or *
- Assess risk level: How verified is this change?
- Find ticket number: See below
- Format:
[prefix] Summarywith ticket on last line
What ships with it
2 files 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.
- yesterday First seen · 139 lines · 73 tokens per session scan A 78bc5c9a3181
commit-notation is a skill published in the GitHub repository quatico-solutions/agent-skills (2 stars, last pushed 7d ago), licensed MIT. It adds 73 tokens to every session and 1,024 once invoked, about $0.0004 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
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…