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 instructions/mrnasil/pnpm-manager/claude-mdgit clone --depth 1 https://github.com/mrnasil/pnpm-managerWrote 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/instructions/mrnasil/pnpm-manager/claude-md)<a href="https://agentmods.dev/instructions/mrnasil/pnpm-manager/claude-md"><img src="https://agentmods.dev/badge/instructions/mrnasil/pnpm-manager/claude-md.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.00541 | $0.00541 |
| Opus 5 | $0.00270 | $0.00270 |
| Sonnet 5 | $0.00108 | $0.00108 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
pnpm-manager CLAUDE.md 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 5d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PNPM Manager Configuration Guide
This file provides instructions for AI agents to help users configure pnpmconfig.json for the PNPM Manager VSCode extension.
Purpose
PNPM Manager reads pnpmconfig.json from the project root to customize behavior: auto-start scripts, custom commands, and notification settings.
Schema
{
"autoStart": {
"enabled": true,
"scripts": ["dev", "dev && test"]
},
"customCommands": [
{
"name": "Full Build",
"command": "build && test && lint",
"description": "Complete build process with tests and linting",
"autoStart": true
}
],
"settings": {
"showNotifications": true,
"autoInstallOnOpen": false
}
}
TypeScript Interface (for reference)
interface PnpmConfig {
autoStart?: {
enabled: boolean; // Enable auto-start feature
scripts: string[]; // Scripts to run automatically on VSCode open
};
customCommands?: Array<{
name: string; // Display name in menu
command: string; // pnpm command to execute (supports &&)
description?: string; // Optional description
autoStart?: boolean; // Whether to run on startup
}>;
settings?: {
showNotifications?: boolean; // Show notification popups (default: true)
autoInstallOnOpen?: boolean; // Run pnpm install on project open (default: false)
};
}
Rules for AI Agents
- When user asks to set up PNPM Manager: Generate
pnpmconfig.jsonin the project root based on theirpackage.jsonscripts. - Script discovery: Read
package.json→scriptsfield to suggest auto-start scripts. - Validation: Ensure JSON is valid and matches the schema above.
- Defaults:
showNotificationsdefaults totrue,autoInstallOnOpendefaults tofalse. Omit from config if default is acceptable. - Complex commands:
commandandscriptssupport&&operators (e.g.,"build && test && lint"). - File location: Always create
pnpmconfig.jsonat the workspace root (same level aspackage.json). - PNPM only: This extension only supports pnpm, not npm or yarn. All commands use
pnpmprefix automatically.
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.
- 5d ago First seen · 61 lines · 541 tokens per session scan A cb64c40a5714
pnpm-manager CLAUDE.md is an instructions file published in the GitHub repository mrnasil/pnpm-manager (2 stars, last pushed 3mo ago), licensed MIT. It adds 541 tokens to every session, about $0.0027 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-31.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).