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 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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<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="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector pass
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.00026 | $0.00273 |
| Opus 5.5 | $0.00010 | $0.00109 |
| Sonnet 5.5 | $0.00005 | $0.00055 |
| Haiku 4.5 | $0.00003 | $0.00027 |
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 10d 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 commit
.commitlintrc.yml is the source of truth: use only the types it allows. Beyond the
specification:
- Keep the header (
type(scope): description) at 72 characters or fewer. - Write the description in the imperative, without a trailing period:
add,fix,bump. Never copy past tense from the request (added,fixed,bumped). - Use the affected area as the scope (
segment,cache,config); omit it for cross-cutting changes. - A change that removes, renames, or alters behavior callers depend on carries both
!after the type or scope and aBREAKING CHANGE:footer. Never one without the other. - Use the body for why, not what, wrapped at 72 characters.
- Review
git diff --cachedand stage files explicitly; nevergit add -A.
feat(segment)!: rename template property StartTime to Start
BREAKING CHANGE: template strings using .StartTime must be updated to .Start
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.
- 10d ago Changed · -79 lines · -21 tokens per session 133bad5f119c
- 1mo 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,614 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 273 once invoked, about $0.0001 per session on Opus 5.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
herdr
Use when the user mentions herdr or is working inside a herdr pane and wants to save/restore a pane layout, change herdr's theme, prefix or other preferences on this host only, start or check on an agent in another herdr pane, add, turn off or open a herdr plugin (file viewer, keybindings), or asks why the herdr…
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.
pixiv-cli-docs
Edit pixiv-cli documentation, AGENTS.md, client bridges, repository maintenance skills, or the distributed product skill. Use when commands, APIs, configuration, architecture, testing, or contributor workflows change and their documentation must stay accurate and portable.
pixiv-cli-release-notes
Prepare pixiv-cli bilingual versioned release notes, audit source coverage, coordinate an authorized version release, or recover its independent publishers. Use for release preparation and historical Release synchronization, not routine feature PR metadata.
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.