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/ikarusmk/aicortex/conventional-commitsnpx skills add IkarusMK/AIcortex --skill conventional-commitsgit clone --depth 1 https://github.com/IkarusMK/AIcortexWrote 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/skills/ikarusmk/aicortex/conventional-commits)<a href="https://agentmods.dev/skills/ikarusmk/aicortex/conventional-commits"><img src="https://agentmods.dev/badge/skills/ikarusmk/aicortex/conventional-commits.svg" alt="Measured on agentmods" 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 | $0.00029 | $0.00288 |
| Opus 5 | $0.00015 | $0.00144 |
| Sonnet 5 | $0.00006 | $0.00058 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
conventional-commits 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 3d 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
Conventional Commits
When to use
Before committing code. Keeps history readable and changelog-friendly.
Format
<type>(<optional scope>): <imperative summary, ≤72 chars>
<body: what changed and WHY, wrapped ~72 cols. Not how — the diff shows how.>
<optional footer: BREAKING CHANGE: …, Refs: #123>
Types
feat (feature) · fix (bug) · refactor · perf · docs · test · chore · ci · build
Rules
- Imperative summary: "add", not "added"/"adds".
- One logical change per commit; split unrelated work.
- The body answers why and notes trade-offs/risks, not a play-by-play.
- Mark breaking changes explicitly in the footer.
Examples
fix: stop double-charging on retried webhooks
Stripe re-sends events on timeout; we keyed off event time, not id, so a
retry created a second charge. Key idempotency on the event id instead.
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.
- 3d ago First seen · 38 lines · 0 tokens per session scan A b83f7a3a86af
conventional-commits is a skill published in the GitHub repository IkarusMK/AIcortex (9 stars, last pushed 14d ago), licensed Apache-2.0. It adds 29 tokens to every session and 288 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-31.
Other skills, from other repositories
checkpoint
End-of-session safety sweep for the kvm-pilot project — "is everything I did this session safe to leave?" Invoke at the end of a work session (or when the user says "checkpoint", "safe to stop?", "wrap up", "am I done here") to verify nothing is quietly unsaved: uncommitted/unpushed code, an unrecorded decision, a…
MCP Server Builder
Step-by-step guidance for creating a new MCP server with FastMCP or the TypeScript SDK — tool definitions, resource handlers, error responses, and usage examples.
Git Commit Writer
Generates conventional commit messages from staged changes or a diff.
pause
Checkpoint the session into git so it survives a close and resumes from any device. Use on "pause", "checkpoint", "cache this session", "save my place", or "I'm stepping away" — writes a handoff, commits work in flight, and pushes.
ci
Create high-quality Git commits for all pending changes.
git-commit
Smart git commit with branch protection, session-aware staging, and conventional commits.