Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/instructions/chrismcdermut/proletariat/claude-md)<a href="https://agentmods.dev/instructions/chrismcdermut/proletariat/claude-md"><img src="https://agentmods.dev/badge/instructions/chrismcdermut/proletariat/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.01409 | $0.01409 |
| Opus 5 | $0.00705 | $0.00705 |
| Sonnet 5 | $0.00282 | $0.00282 |
| Haiku 4.5 | $0.00141 | $0.00141 |
Grade B, and why
proletariat 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 6d 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
// 2. Handle JSON mode FIRST - output prompt config and return How it starts
The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Context
Build & Package Manager
Use pnpm not npm
pnpm install # Install dependencies
pnpm run build # Build all packages
pnpm -r build # Build recursively
Project Structure
This is a pnpm monorepo workspace:
apps/
cli/ # Main CLI tool (prlt command)
src/
commands/ # oclif commands
lib/ # Shared utilities
docs/ # Documentation
pmo/ # Project management office templates
scripts/ # Build and utility scripts
specs/ # Specification files
Key Patterns
- Commands: Use oclif framework in
apps/cli/src/commands/ - Database: SQLite via better-sqlite3 in
apps/cli/src/lib/database/ - Themes: Optional agent naming themes in
apps/cli/src/lib/themes.ts
Testing
pnpm test # Run all tests (unit + e2e)
pnpm test:unit # Run unit tests only
pnpm test:e2e # Run e2e tests only
pnpm test:smoke # Run smoke tests
Important: Always verify the build passes after modifying TypeScript files in apps/cli/:
cd apps/cli && pnpm build
Every bug fix PR MUST include a regression test that fails if the fix is reverted.
Every PR MUST include tests for changed code. No exceptions.
- Write unit tests for new functions and modified logic
- Write integration tests for new flows and command changes
- Test files live in
apps/cli/test/unit/andapps/cli/test/e2e/ - If you modify source code without adding or updating tests, your PR will be blocked
Command Code Rules
- Never call
process.exit()in command code — let oclif handle lifecycle (usereturninstead).
Provider Architecture
All ticket operations MUST go through the TicketProvider interface (src/lib/providers/types.ts). Never call PMO storage directly for ticket reads/writes.
- Use
resolveTicketProvider()orresolveProjectProvider()fromsrc/lib/providers/resolver.tsto get the correct provider - Local PMO is just another provider (implements
TicketProvider), not a cache or intermediary - Linear is the source of truth when configured — prlt reads and writes directly to Linear API
- Never sync/mirror Linear data into PMO — they are parallel providers, not a pipeline
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.
- 6d ago First seen · 189 lines · 1,409 tokens per session scan B 46a39e82e02a
proletariat CLAUDE.md is an instructions file published in the GitHub repository chrismcdermut/proletariat (35 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 1,409 tokens to every session, about $0.0070 per session on Opus 5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.
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).
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.