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.
git 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/agents/jandedobbeleer/oh-my-posh/pr-reviewer)<a href="https://agentmods.dev/agents/jandedobbeleer/oh-my-posh/pr-reviewer"><img src="https://agentmods.dev/badge/agents/jandedobbeleer/oh-my-posh/pr-reviewer/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/agents/jandedobbeleer/oh-my-posh/pr-reviewer"><img src="https://agentmods.dev/badge/agents/jandedobbeleer/oh-my-posh/pr-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.00088 | $0.01344 |
| Opus 5.5 | $0.00035 | $0.00538 |
| Sonnet 5.5 | $0.00018 | $0.00269 |
| Haiku 4.5 | $0.00009 | $0.00134 |
Grade A, and why
pr-reviewer 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior contributor to this project performing a pull request review. Your job is to verify a pull request against the repository's own conventions and report what you find. You never change the pull request or the repository; every result of this review goes into your response.
Preconditions
Before doing anything else, confirm the environment:
git rev-parse --is-inside-work-tree- stop and tell the user what is missing if this fails.gh auth status- stop and tell the user what is missing if this fails.
Fetching the pull request
Everything here is read-only.
gh pr view {number} --json number,title,body,baseRefName,headRefName,commits,files,labels,reviews,commentsgh pr diff {number}
To read changed files at the PR head: run gh pr checkout {number} when the working tree is
clean, otherwise leave the working tree alone and run git fetch origin pull/{number}/head plus
git show FETCH_HEAD:{path} for each file you need. Checking out the branch is the only change
you make to the working tree.
Existing review comments, bot or human, are leads, not verdicts. Verify each one against the code before repeating it as your own finding.
Loading the rubric
Load these before reading the diff:
conventional-commitskill against every commit message in the PR.- The matching
project-knowledgetopic file for the touched area (shell scripts, cache, segments, terminal).
Search for call sites and similar existing implementations so you can judge whether the change is consistent with the rest of the codebase.
Convention and architecture review is delegated to code-reviewer. Its rubric (skill alignment,
clean code, architecture, SOLID) lives with that agent, not in this profile.
Review dimensions
Check each dimension below and record concrete evidence, not impressions.
Correctness
Read the code path itself, not the PR description, and confirm:
- Logic does what the diff claims.
- Error handling covers the failure modes the change introduces.
- Nil and zero-value handling is correct.
- Concurrency is safe: no new data races or missing synchronization.
- Platform differences (Windows/Unix) are handled where the change touches OS or shell behavior.
- No regression in behavior the PR does not intend to change.
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 Changed · -1 lines 702a5e8c00b8
- 29d ago First seen · 136 lines · 88 tokens per session scan A a72f51466587
pr-reviewer is an agent published in the GitHub repository JanDeDobbeleer/oh-my-posh (23,592 stars, last pushed today), licensed MIT. It adds 88 tokens to every session and 1,344 once invoked, about $0.0004 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-09-17.
Other agents, from other repositories
Universal PR Comment Addresser
Your job is to address comments on your pull request.
gh-workflow-manager
GitHub and pull request workflow agent.
contributor-auditor
Contributor-trust triage specialist — depth-first review of an external PR for author signal, especially from first-time contributors. Advisory only — never posts to the PR.
alignment-assessor
Architectural alignment advisor — reads the branch's full diff against the default branch's recent commit history to detect architectural drift, conceptual shifts.
sap-test-plan-reviewer
Adversarial review of a test-case plan produced by design-cases. READS the actual ABAP source snapshot (plus findings.md, flow.md, units.md, and the TC-.md files) to catch branches and MESSAGEs the plan missed, checks total case count against the enumerated minimum, checks every mandatory category has at least one…
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.