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/dfinke/psai/claude-mdgit clone --depth 1 https://github.com/dfinke/PSAIWrote 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/dfinke/psai/claude-md)<a href="https://agentmods.dev/instructions/dfinke/psai/claude-md"><img src="https://agentmods.dev/badge/instructions/dfinke/psai/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 | $0.00284 | $0.00284 |
| Opus 5 | $0.00142 | $0.00142 |
| Sonnet 5 | $0.00057 | $0.00057 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
PSAI 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 4d 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
PSAI Project Conventions
Build & Development Commands
- Install Dependencies:
Import-Module ./PSAI.psd1 -Force - Run Tests:
Invoke-Pester ./Tests(Ensure Pester 5.x is used) - Static Analysis:
Invoke-ScriptAnalyzer -Path ./PSAI.psm1 - Build Module:
./Build/BuildModule.ps1(if applicable)
Engineering Standards & Patterns
- Architecture: Follow High-Agency Agent patterns. Decouple LLM logic from PowerShell provider logic.
- TDD: All new features or bug fixes must include a corresponding Pester test in the
/Testsdirectory. - Style: Follow the PowerShell Practice and Style Guide.
- Naming: Use standard
Verb-Nounpairs. Avoid aliases in module code. - Error Handling: Use
try/catchblocks for all API calls; provide meaningful error objects to the LLM context.
Agentic Workflow
- When refactoring, maintain the "Be the Automator, Not the Automated" philosophy.
- Tools should be modular and discoverable via
Get-Command -Module PSAI. - Reference the
ConvertTo-AIPromptlogic when packaging codebase context for LLM windows.
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.
- 4d ago First seen · 19 lines · 284 tokens per session scan A e91c01029dbf
PSAI CLAUDE.md is an instructions file published in the GitHub repository dfinke/PSAI (270 stars, last pushed 5mo ago), licensed MIT. It adds 284 tokens to every session, about $0.0014 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
scaffolding CLAUDE.md
Instructions for komluk/scaffolding, covering protocol, agents (13), decision tree and key rules.
automatos-ai CLAUDE.md
Claude Code instructions for AutomatosAI/automatos-ai, covering claude.md — automatos ai platform, 1. where this project is, 2. default mindset: reuse over build, 3. prd framing — what type is this? and 4. clean-coding rules (automatos-specific).
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.
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.