oh-my-posh is a customizable prompt theme engine that renders command-line prompts across shells and platforms. Developers and terminal users use it to configure primary, secondary, right, and transient prompts in shells such as PowerShell, zsh, Bash, and cmd. The catalogue entries provide skills, instructions, agents, and an MCP integration for working with oh-my-posh.
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/jandedobbeleer/oh-my-posh/conventional-commitnpx skills add JanDeDobbeleer/oh-my-posh --skill conventional-commitgit clone --depth 1 https://github.com/JanDeDobbeleer/oh-my-poshWrote 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/jandedobbeleer/oh-my-posh/conventional-commit)<a href="https://agentmods.dev/skills/jandedobbeleer/oh-my-posh/conventional-commit"><img src="https://agentmods.dev/badge/skills/jandedobbeleer/oh-my-posh/conventional-commit.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.1 | $0.00047 | $0.01076 |
| Opus 5 | $0.00023 | $0.00538 |
| Sonnet 5 | $0.00009 | $0.00215 |
| Haiku 4.5 | $0.00005 | $0.00108 |
Grade A, and why
conventional-commit 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 6d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conventional Commit
Commit Message Structure
<type>(<scope>): <description>
[optional body]
[optional footer(s)]
Types
| Type | When to use |
|---|---|
feat |
A new feature |
fix |
A bug fix |
docs |
Documentation changes, no code |
style |
Formatting, missing semicolons, etc. (no logic change) |
refactor |
Code change that is neither a fix nor a feature |
perf |
Performance improvement |
test |
Adding or correcting tests |
ci |
CI configuration changes |
chore |
Maintenance tasks (updating deps, tooling, etc.) |
revert |
Reverts a previous commit |
Append ! after the type/scope to signal a breaking change: feat!: or feat(api)!:
When a change breaks existing behavior, both markers are mandatory: the ! suffix on the type
and the BREAKING CHANGE: footer. They always appear together — never one without the other.
Scope
Optional. Use the name of the area affected, e.g., segment, cache, config, ui.
Omit when the change is truly cross-cutting.
Description
- Required. One short imperative sentence, no period at the end. The full header line (type + scope + description) must be 72 characters or fewer. Aim for 50 characters or fewer for the description itself — this almost always keeps the full header within budget regardless of type and scope length.
- Use the imperative mood: "add", not "added" or "adds". Never past tense or present-third-person:
✗
added,fixed,bumped,implemented→ ✓add,fix,bump,implement. - Never mirror the input's phrasing. If the request uses past-tense words (
updated,added,bumped,was removed,got regenerated), convert them to imperative before writing the description:update,add,bump,remove,regenerate.
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.
- 6d ago First seen · 109 lines · 47 tokens per session scan A 05f6b10c1909
conventional-commit is a skill published in the GitHub repository JanDeDobbeleer/oh-my-posh (23,423 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 1,076 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-30.
Other skills, from other repositories
pixiv-cli-docs
Maintain pixiv-cli README, locale contracts, maintainer documentation, contribution guidance, and documentation checks. Use when adding, changing, reviewing, or routing repository documentation; use pixiv-cli-release-notes for versioned bilingual changelog or release-prep work.
pixiv-cli-release-notes
Audit pixiv-cli release sources, write and validate bilingual Markdown release notes, publish immutable tags, synchronize historical GitHub Release bodies, and hand off SkillHub/ClawHub verification. Use for release preparation, version selection, tag publication, release monitoring, or historical note synchronization.
release-sync
PromptHub release update skill. Use for /update-readme, version bumps, changelog updates, website sync, GUI screenshot/doc refresh, and multilingual release/documentation alignment.
use-notion
Reference for using the Notion API via the notion-agent subagent. Use to expore and update Notion workspace content.
storywriter
Write well-formed work items (Tasks, User Stories, Issues) for Azure DevOps, GitHub, or Jira. Use this skill when asked to write, draft, or create a task, story, issue, or work item.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.