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 espennilsen/pi --skill pi-projectsgit clone --depth 1 https://github.com/espennilsen/piWrote 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/espennilsen/pi/pi-projects)<a href="https://agentmods.dev/skills/espennilsen/pi/pi-projects"><img src="https://agentmods.dev/badge/skills/espennilsen/pi/pi-projects/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/espennilsen/pi/pi-projects"><img src="https://agentmods.dev/badge/skills/espennilsen/pi/pi-projects.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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.00016 | $0.00278 |
| Opus 5.5 | $0.00006 | $0.00111 |
| Sonnet 5.5 | $0.00003 | $0.00056 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
pi-projects 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 1mo 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
Pi Projects Extension
Auto-discovers git repos and provides a tracking dashboard.
Setup
Install the extension, then access:
- Web dashboard at
/projectsvia pi-webserver /projectscommand for quick statusprojectstool for the LLM
Configuration (settings.json)
{
"pi-projects": {
"devDir": "~/Dev",
"autoScan": true
}
}
- devDir: Primary directory to scan for projects (default: ~/Dev)
- autoScan: Auto-discover repos on startup
Tool Actions
projects list— Show all projects with git statusprojects scan— Rescan directoriesprojects hide --path /path— Hide a project from the dashboardprojects unhide --path /path— Restore a hidden projectprojects sources— List scan directoriesprojects sources --path /new/dir— Add a scan directory
Web Dashboard Features
- Card and table views with search/filter/sort
- Git status: branch, last commit, dirty count, ahead/behind
- Manage modal: add scan directories, hide/show projects
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.
- 1mo ago First seen · 45 lines · 16 tokens per session scan A c03b3a41e801
pi-projects is a skill published in the GitHub repository espennilsen/pi (122 stars, last pushed 9d ago), licensed MIT. It adds 16 tokens to every session and 278 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
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
cuga-github-issues
Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking. Use when the user says create new issues, report a bug, file a bug, feature request, new feature, create an epic, GitHub issue, sub-issue…