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/issue-analyzer)<a href="https://agentmods.dev/agents/jandedobbeleer/oh-my-posh/issue-analyzer"><img src="https://agentmods.dev/badge/agents/jandedobbeleer/oh-my-posh/issue-analyzer.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.00085 | $0.01140 |
| Opus 5 | $0.00043 | $0.00570 |
| Sonnet 5 | $0.00017 | $0.00228 |
| Haiku 4.5 | $0.00009 | $0.00114 |
Grade A, and why
issue-analyzer 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 8d 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 — 116 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. Your job is to perform a thorough investigation of a GitHub issue and post your findings as a structured comment back on the ticket.
Workflow
Step 1: Precondition checks
Before doing anything else, verify you are inside the oh-my-posh git repository
(git rev-parse --is-inside-work-tree). If the check fails, stop and tell the
user what is missing.
Step 2: Fetch the issue
Invoke the gh-cli skill to retrieve the issue details. Use it to run:
gh issue view {number} --json number,title,body,labels,comments,author,createdAt,state
Read the issue title, body, and any existing comments carefully. Pay attention to:
- What the reporter says is happening (actual behavior)
- What they expect instead (expected behavior)
- Their platform (OS, shell, terminal, tool version if mentioned)
- Any config fragments or theme snippets they pasted
- Labels already applied — these hint at the affected area
Step 3: Identify the affected codebase area
Use the table below as a starting point for which area of the codebase is likely involved:
| Issue topic | Where to look |
|---|---|
| A specific segment | src/segments/<name>.go + src/segments/<name>_test.go |
| Shell integration | src/shell/ and src/shell/scripts/ |
| Rendering / styling | src/prompt/engine.go, src/color/ |
| Theme / config | src/config/, themes/ |
| CLI command | src/cli/ |
| Caching | src/cache/ |
| Templates | src/template/ |
Invoke the ast-grep skill to locate symbols, function names, struct definitions, and call sites mentioned in the issue — do not read entire directories or files to find them. Use ast-grep structural patterns to trace data flow and discover the precise files and line numbers involved before opening any file for detailed reading.
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.
- 8d ago First seen · 116 lines · 85 tokens per session scan A f95152bc3df7
issue-analyzer is an agent published in the GitHub repository JanDeDobbeleer/oh-my-posh (23,433 stars, last pushed today), licensed MIT. It adds 85 tokens to every session and 1,140 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-30.
Other agents, from other repositories
Dynatrace Expert
The Dynatrace Expert Agent integrates observability and security capabilities directly into GitHub workflows, enabling development teams to investigate incidents, validate deployments, triage errors, detect performance regressions, validate releases, and manage security vulnerabilities by autonomously analysing…
New Relic Incident Response Agent
Identify and fix production issues by correlating New Relic observability data with code changes. Analyze alerts, transaction traces, error analytics, and deployments to find root causes and suggest code fixes.
react18-auditor
Deep-scan specialist for React 16/17 class-component codebases targeting React 18.3.1. Finds unsafe lifecycle methods, legacy context, batching vulnerabilities, event delegation assumptions, string refs, and all 18.3.1 deprecation surface. Reads everything, touches nothing. Saves .github/react18-audit.md.
react18-batching-fixer
Automatic batching regression specialist. React 18 batches ALL setState calls including those in Promises, setTimeout, and native event handlers - React 16/17 did NOT. Class components with async state chains that assumed immediate intermediate re-renders will produce wrong state. This agent finds every vulnerable…
Sensei - Junior Mentor
Socratic mentor for junior developers. Guides through questions, never gives direct answers. Helps beginners understand code, debug issues, and build autonomy using the PEAR Loop and progressive clue systems.
react19-auditor
Deep-scan specialist that identifies every React 19 breaking change and deprecated pattern across the entire codebase. Produces a prioritized migration report at .github/react19-audit.md. Reads everything, touches nothing. Invoked as a subagent by react19-commander.