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/rosudrag/ai-praxis/agents-mdgit clone --depth 1 https://github.com/rosudrag/ai-praxisWrote 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/rosudrag/ai-praxis/agents-md)<a href="https://agentmods.dev/instructions/rosudrag/ai-praxis/agents-md"><img src="https://agentmods.dev/badge/instructions/rosudrag/ai-praxis/agents-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.01916 | $0.01916 |
| Opus 5 | $0.00958 | $0.00958 |
| Sonnet 5 | $0.00383 | $0.00383 |
| Haiku 4.5 | $0.00192 | $0.00192 |
Grade A, and why
ai-praxis AGENTS.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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Praxis - Development Instructions
This file contains instructions for developing and improving THIS repository itself.
If you're here to bootstrap another project, see bootstrap/AGENTS.md instead.
Project Purpose
This repository is a comprehensive methodology system for AI coding assistants. When users point their AI tool at this repo, it reads the instructions in /bootstrap and uses them to set up the praxis system in the user's own project.
Supported Tools: Claude Code, Cursor, Windsurf, Cline, and other MCP-compatible AI assistants.
Guiding Principles
- Tool-agnostic first - AGENTS.md is the primary format; CLAUDE.md is a forwarding shim. Every feature must work across tools, with tool-specific branches only where unavoidable.
- Methodology over config - We teach patterns and principles, not dump config files. The bootstrap should make the user's project self-sufficient.
- Progressive disclosure - Don't overwhelm. Start with what matters most, let users discover depth as they need it.
- Minimal footprint - Generate only what the project needs. No bloat, no unused templates, no speculative features.
- Idempotent and safe - Running bootstrap twice should not break anything or duplicate content.
What This Repo Is NOT
- Not a plugin - We don't ship runtime code that hooks into AI tools
- Not a config dump - We don't copy dozens of files into
~/.claude/ - Not Claude-specific - Despite the CLAUDE.md shim, the system targets all AI coding assistants
- Not prescriptive about stack - We detect and adapt to the user's tech stack, not impose one
Repository Structure
ai-praxis/
├── AGENTS.md # You are here (meta instructions)
├── CLAUDE.md # Forwarding file for Claude Code
├── README.md # Human documentation
├── examples/ # Real-world AGENTS.md examples by stack
├── tasks/ # Backlog of improvement ideas (gitignored)
└── bootstrap/
├── AGENTS.md # Entry point router (mode selection)
├── .state/ # Environment setup state
│ ├── .gitkeep
│ └── environment-state.template.json
├── environment/ # Mode 1: Environment setup (global tools)
│ ├── AGENTS.md # Environment orchestrator
│ └── procedures/
│ ├── 01-install-serena.md
│ ├── 02-install-mcp-servers.md
│ └── 03-install-agents.md
├── project/ # Mode 2: Project bootstrap (project files)
│ ├── AGENTS.md # Project orchestrator
│ ├── procedures/
│ │ ├── 00-analyze-project.md
│ │ ├── 01-generate-agents-md.md
│ │ ├── 02-generate-docs.md
│ │ ├── 03-setup-adrs.md
│ │ └── 04-setup-contexts-commands-agents.md
│ └── verification.md # Post-bootstrap verification
├── templates/ # Shared templates for both modes
│ ├── AGENTS.md.template
│ ├── adr-template.md
│ ├── agents/ # Agent definition templates
│ ├── commands/ # Slash command templates
│ ├── contexts/ # Behavior mode templates (dev, review, research)
│ ├── guides/ # Guide templates (TDD, code quality, etc.)
│ ├── hooks/ # Hook script templates (Claude Code)
│ ├── hooks.json.template # Hook config template
│ └── rules/ # Rule templates (common + language-specific)
│ └── common/ # Language-agnostic rules
└── reference/ # Shared reference docs
├── guardrail-principles.md
├── serena-best-practices.md
└── token-optimization.md
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 · 169 lines · 1,916 tokens per session scan A b87e24c02df0
ai-praxis AGENTS.md is an instructions file published in the GitHub repository rosudrag/ai-praxis (2 stars, last pushed 5mo ago), licensed MIT. It adds 1,916 tokens to every session, about $0.0096 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).