Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mitkox/SkillOptnpx agentmods add skills/mitkox/skillopt/pi-skilloptWrote 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/mitkox/skillopt/pi-skillopt)<a href="https://agentmods.dev/skills/mitkox/skillopt/pi-skillopt"><img src="https://agentmods.dev/badge/skills/mitkox/skillopt/pi-skillopt/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/mitkox/skillopt/pi-skillopt"><img src="https://agentmods.dev/badge/skills/mitkox/skillopt/pi-skillopt.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.00059 | $0.01060 |
| Opus 5.5 | $0.00024 | $0.00424 |
| Sonnet 5.5 | $0.00012 | $0.00212 |
| Haiku 4.5 | $0.00006 | $0.00106 |
Grade A, and why
pi-skillopt 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 2mo 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PI SkillOpt Operator
Use this skill when the user wants the agent to operate the SkillOpt repository: run experiments, evaluate skills, configure local models, inspect outputs, or extend the repo with new benchmarks/backends.
Core repo facts
- SkillOpt optimizes a skill document / system prompt, not model weights.
- The repo supports a generic local OpenAI-compatible backend named
openai_compat. - The local example model config is
configs/dotnetdebug/local_mitko.yaml. - That config uses model
mitkoathttp://localhost:8000/v1for both optimizer and target. - The runnable sample benchmark is
dotnetdebug. - The sample dataset is
data/dotnetdebug/tasks.json. - The seed skill is
skillopt/envs/dotnetdebug/skills/initial.md. - Training entry point:
scripts/train.py. - Eval-only entry point:
scripts/eval_only.py.
Default workflow
- Identify the user goal:
- run a SkillOpt training job
- evaluate an existing skill
- inspect outputs from a previous run
- add or modify a benchmark
- add or modify a backend
- Confirm the benchmark, backend, target model, and desired output directory.
- Prefer a small smoke test first before a larger run.
- Use existing configs when possible instead of inventing new ones.
- After a run, report:
- exact command used
- output directory
- best skill path
- headline metrics
- next recommended action
Local model workflow
When the user asks to use a local model or mentions mitko, localhost:8000, or an OpenAI-compatible endpoint:
- Prefer
model.backend: openai_compat. - Set both
optimizer_backendandtarget_backendtoopenai_compatunless the user explicitly wants a mixed setup. - Use
configs/dotnetdebug/local_mitko.yamlwhen the task is the built-in dotnet debugging example. - Keep smoke tests small, for example:
train.num_epochs=1train.batch_size=2gradient.analyst_workers=1gradient.minibatch_size=2env.workers=1env.limit=2
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.
- 2mo ago First seen · 124 lines · 59 tokens per session scan A 53f525e9f9fd
pi-skillopt is a skill published in the GitHub repository mitkox/SkillOpt (86 stars, last pushed 5mo ago), licensed MIT. It adds 59 tokens to every session and 1,060 once invoked, about $0.0002 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…