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/project-knowledgenpx skills add JanDeDobbeleer/oh-my-posh --skill project-knowledgegit clone --depth 1 https://github.com/JanDeDobbeleer/oh-my-poshWhat 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.00081 | $0.00677 |
| Opus 5 | $0.00041 | $0.00338 |
| Sonnet 5 | $0.00016 | $0.00135 |
| Haiku 4.5 | $0.00008 | $0.00068 |
Grade A, and why
project-knowledge 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Knowledge
A modular memory of hard-won, verified facts about this codebase and its runtime environments. Everything here was learned the expensive way - through debugging, benchmarking, or reproduction - and is not derivable from a quick read of the code.
How to use
- Identify which topics the task touches (a zsh script change touches
zshand probablytesting; a segment bug touchescodebase). - Read those reference files before writing code or designing an experiment.
- Treat entries as point-in-time observations: they carry dates, and code moves. Verify a claim against the current code before building on it, and fix the entry when it drifted.
Topics
| Topic | Read when |
|---|---|
| codebase | Touching Go code: segments, cache, templates, streaming, serve daemon |
| zsh | Touching omp.zsh, zle widgets, coproc, or zsh plugin interop |
| pwsh | Touching omp.ps1, PSReadLine, runspaces, events, or pwsh perf |
| fish | Touching omp.fish, fish jobs, fifos, or fish event handlers |
| bash | Touching omp.bash, PROMPT_COMMAND, readline, or bash coprocs |
| cmd-clink | Touching omp.lua, Clink integration, or Windows pipe lifecycles |
| terminal | Reasoning about ptys, ConPTY, Windows Terminal, or terminal encoding |
| testing | Building a harness to drive a shell end-to-end (WSL, zpty, script(1)) |
How to maintain
This is a living memory - extend it whenever a session ends with knowledge worth keeping:
- Add durable, verified facts only: gotchas, platform quirks, measured numbers, failed approaches worth not retrying. No speculation, no session-specific state.
- Date non-obvious claims (
verified 2026-07-14) so future readers can judge staleness. - One topic per file. Append to the matching reference file; create a new file and index row when a fact fits no existing topic.
- Prefer updating or deleting a stale entry over stacking corrections on top of it.
- Keep entries self-contained: name the file, function, or command they apply to.
- This skill is committed - include knowledge updates in the commit of the change they relate to.
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 49 lines · 81 tokens per session scan A f8fe0878cc71
project-knowledge is a skill published in the GitHub repository JanDeDobbeleer/oh-my-posh (23,372 stars, last pushed yesterday), licensed MIT. It adds 81 tokens to every session and 677 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 skills, from other repositories
db
Database schema and query conventions for ThunderID. Use when changing schema scripts, defining SQL queries, updating store constants, or reviewing deployment-scoped persistence rules.
console
Navigate and interact with the ThunderID Console UI. Use when exploring the ThunderID admin console, testing UI changes, creating users/applications/roles, or debugging the frontend.
docs
Handles every ThunderID documentation task in one skill: scaffolding a new page, writing content into an existing page, checking structural standards, reviewing writing quality/tone/AI-vocabulary, verifying technical accuracy, reviewing API documentation (OpenAPI specs and SDK reference pages) for consistency and…
new-config
Interactively scaffold a new smug tmux session configuration (a YAML template). Use when the user wants to create, scaffold, or set up a new smug project/config file, or asks for "smug new config", "a smug template", or "/new-config". Walks the user through session name, root, windows, panes, commands, env, and hooks…
spec-init
面向新项目或现有项目的文档驱动开发 skill。Use when the user wants to create, 补齐, 更新, or refine project specs, run a Spec Kit-inspired workflow loop, maintain workflow/knowledge/change docs, analyze consistency, converge implementation back into docs, or update README/AGENTS for a real project.
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.