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/vxcontrol/pentagi/claude-mdgit clone --depth 1 https://github.com/vxcontrol/pentagiWhat 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 | $0.02308 | $0.02308 |
| Opus 5 | $0.01154 | $0.01154 |
| Sonnet 5 | $0.00462 | $0.00462 |
| Haiku 4.5 | $0.00231 | $0.00231 |
Grade A, and why
pentagi 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 2d 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 — 159 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.
Core Interaction Rules
- Always use English for all interactions, responses, explanations, and questions with users.
- Password Complexity Requirements: For all password-related development (registration, password reset, API token generation, etc.), enforce the same policy in both backend and frontend — never rely on frontend validation alone. Source of truth, keep the two in sync:
backend/pkg/server/models/init.go→strongPasswordValidatorStringandfrontend/src/features/authentication/password-change-form.tsx(zod schema). The policy:- Length 8–72 characters (72 bytes, the most bcrypt will hash — a longer value fails inside
bcrypt.GenerateFromPassword, after validation). - A password is valid if it is either 16+ characters (any composition), or 8–15 characters containing at least 1 lowercase letter, 1 uppercase letter, 1 number, and 1 special character from
!@#$&*.
- Length 8–72 characters (72 bytes, the most bcrypt will hash — a longer value fails inside
Project Overview
PentAGI is an automated security testing platform powered by AI agents. It runs autonomous penetration testing workflows using a multi-agent system (Researcher, Developer, Executor agents) that coordinates LLM providers, Docker-sandboxed tool execution, and a persistent vector memory store.
The application is a monorepo with:
backend/— Go REST + GraphQL API serverfrontend/— React + TypeScript web UIobservability/— Optional monitoring stack configs
Build & Development Commands
Backend (run from backend/)
go mod download # Install dependencies
go build -trimpath -o pentagi ./cmd/pentagi # Build main binary
go test ./... # Run all tests
go test ./pkg/foo/... -v -run TestName # Run specific test
golangci-lint run --timeout=5m # Lint
# Code generation (run after schema changes)
go run github.com/99designs/gqlgen --config ./gqlgen/gqlgen.yml # GraphQL resolvers
swag init -g ../../pkg/server/router.go -o pkg/server/docs/ --parseDependency --parseInternal --parseDepth 2 -d cmd/pentagi # Swagger docs
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.
- 2d ago First seen · 159 lines · 2,308 tokens per session scan A 395692e23079
pentagi CLAUDE.md is an instructions file published in the GitHub repository vxcontrol/pentagi (22,176 stars, last pushed 26d ago), licensed MIT. It adds 2,308 tokens to every session, about $0.0115 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-30.
Other instructions, from other repositories
zeroshot CLAUDE.md
Claude Code instructions for the-open-engine/zeroshot, covering zeroshot: multi-agent coordination engine, 🔴 critical rules, 🔴 general purpose requirement (critical), 🔴 behavioral standards and where to look.
Upsonic CLAUDE.md
Claude Code instructions for Upsonic/Upsonic, covering claude.md, project overview, ai operational guides, default pre-work consultation and keep documents/ai/explanation/ in sync with code.
agentsys CLAUDE.md
Claude Code instructions for agent-sh/agentsys, covering agentsys, critical rules, model selection, core priorities and dev commands.
vizra-adk CLAUDE.md
Instructions for vizra-ai/vizra-adk, covering vizra adk - laravel ai agent development kit, project overview, key concepts, agents and tools.
agentic-os AGENTS.md
Instructions for modimihir07/agentic-os, covering agentic os — complete project context for ai agents, role definition, project identity, architecture and 3-agent engine.
AIPass CLAUDE.md
Instructions for AIOSAI/AIPass, covering aipass, startup protocol and memories.