piolium: Instructions file for Claude Code

CLAUDE.md

piolium CLAUDE.md is an instructions file for Claude Code from vigolium/piolium. It costs 2,509 tokens per session, scanned B, original, MIT.

Repository guidance for Piolium, a plugin for the Pi coding agent. It explains the project layout, commands, tests, and ways to load the plugin during development.

In plain words
What is it for?
Understanding the repository, installing dependencies, checking code, running one test or a named test, and loading the extension locally.
Why use it?
It gives an agent or developer the project-specific instructions needed to work safely and run checks without guessing commands or setup.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions subagents; mentions Claude Code.

This is vigolium/piolium's own configuration. It tells Claude Code how to work on piolium itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything piolium configures →

Reuse

Borrowing it

Nothing to install: this file belongs to vigolium/piolium. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/vigolium/piolium/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/vigolium/piolium

Made for: Claude Code.

Wrote 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.

agentmods badge for piolium CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/vigolium/piolium/claude-md/github.svg)](https://agentmods.dev/instructions/vigolium/piolium/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/vigolium/piolium/claude-md"><img src="https://agentmods.dev/badge/instructions/vigolium/piolium/claude-md/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.

agentmods 80×15 button for piolium CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/vigolium/piolium/claude-md"><img src="https://agentmods.dev/badge/instructions/vigolium/piolium/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,509 This file is loaded in full into every session.
When invoked 2,509 The same file — it is already loaded in full.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.02509 $0.02509
Opus 5.5 $0.01004 $0.01004
Sonnet 5.5 $0.00502 $0.00502
Haiku 4.5 $0.00251 $0.00251

Measured 1mo ago against content hash b7efc504fd9e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

piolium CLAUDE.md scanned grade B with 1 finding 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.

Unrestricted tool accessmediumExcessive agency

A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.

Pi packages execute arbitrary code: extensions run TypeScript, skills can instruct the model to run any shell command, and the bundled audit agents declare `bash`, `write`, and `edit` tools. Treat this package as trusted
CLAUDE.md · 99 lines

How it starts

The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Project at a glance

Piolium is a Pi extension (a plugin for @earendil-works/pi-coding-agent) that ships a multi-phase repository security audit pipeline. It is not a standalone CLI — it's loaded into a pi session, which then exposes the /piolium-* slash commands defined here. The bundled sub-agents (agents/) and skills (skills/) are committed to the repo.

Runtime is Bun ≥1.1.0 (see package.json#engines). All Pi SDK packages are listed as peerDependencies and provided by the host pi process.

Commands

bun install
bun run typecheck   # tsc --noEmit
bun run lint        # biome check .
bun run format      # biome format --write .
bun run test        # vitest run (fileParallelism: false — audit-state tests touch real fs)

# Run a single test file or filter by name
bun run test -- test/scheduler.test.ts
bun run test -- -t "phase status strip"

# Dev install into Pi (edits in this checkout land immediately, no reinstall)
pi install ./
# Or load the extension ad-hoc without touching settings:
pi -e ./extensions/piolium/index.ts

Driving the extension once installed: pi -p "/piolium-balanced --fresh" (one-shot) or start pi and type /piolium-status. End-to-end harness check: /piolium-smoke.

Architecture

Extension surface (extensions/piolium/index.ts)

The default export pioliumExtension(pi) is the single entry point Pi calls per session. It:

  1. Registers session flags (--plm-dir, --plm-since, --plm-scan-limit, --plm-scan-since, and the --plm-*-retries/--plm-*-backoff* family). Each flag mirrors to a PIOLIUM_* env var via applyPioliumProcessFlagEnv so downstream modules read a single source of truth (process.env).
  2. Registers a piolium-stream message renderer that pretty-prints sub-agent tool-call/result events nested under the originating phase tag.
  3. Registers each /piolium-* slash command. Every handler delegates to a mode runner under extensions/piolium/modes/ and wires phase-strip UI through createPhaseStripCommandUi.
  4. Registers the bundled anthropic-vertex provider (providers/anthropic-vertex.ts), but only when Vertex looks configured — isAnthropicVertexConfigured() gates it on the PIOLIUM_VERTEX override or any Google/Vertex env var, so a plain install doesn't advertise a provider it can't authenticate. PIOLIUM_VERTEX is read straight from process.env (no --plm-* flag): flag env mirroring runs during command parsing, which is after this init-time registration, so a flag couldn't take effect here.

Read the full file on GitHub · 99 lines

Changes

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.

  1. 1mo ago Changed · +6 lines · +431 tokens per session b7efc504fd9e
  2. 1mo ago First seen · 93 lines · 2,078 tokens per session scan B f28a969cfe3f

Subscribe to this mod's changes

piolium CLAUDE.md is an instructions file published in the GitHub repository vigolium/piolium (145 stars, last pushed 1mo ago), licensed MIT. It adds 2,509 tokens to every session, about $0.0100 per session on Opus 5.5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,786 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens