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/facets-cloud/praxis-cli/claude-mdgit clone --depth 1 https://github.com/Facets-cloud/praxis-cliWhat 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.04765 | $0.04765 |
| Opus 5 | $0.02382 | $0.02382 |
| Sonnet 5 | $0.00953 | $0.00953 |
| Haiku 4.5 | $0.00477 | $0.00477 |
Grade A, and why
praxis-cli 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 — 357 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — praxis-cli
Guidance for Claude Code (and other AI assistants) working in this repo.
Project-specific overrides for the global ~/.claude/CLAUDE.md.
Project overview
Single-binary Go CLI (praxis) that exposes Praxis cloud capabilities to
any local AI host (Claude Code, Cursor, Gemini CLI). The CLI is a thin
HTTPS client to a Praxis cloud deployment — it does not run an agent
loop locally. Skills are sourced (fetched + nomenclature-translated) into
the user's AI host; MCP tools execute server-side under org-managed
credentials. See README.md for the user-facing story.
Design principle — single-profile users first
The typical praxis user has ONE profile (a customer on one control plane); everything must resolve silently to "default" for them. Multi-profile users (Facets engineers, support) are power users: their flows must work, but they are strictly secondary and must never regress the single-profile flow. Concretely:
- New flags and subcommands are opt-in; the default flow never grows required steps, prompts, or warnings a single-profile user would see.
- Power-user affordances (profile pins, raptor cross-checks, per-directory profiles) live behind flags or status fields that stay inert when only one profile exists.
- When a trade-off pits multi-profile ergonomics against single-profile cleanliness, single-profile wins.
Match this repo, and keep it small
Before adding anything, open 2-3 existing files that do the same job and copy their shape. A diff that reads like a different person wrote it is a review cost even when the logic is right.
- Smallest diff that works. Fewest files, fewest new packages. Extending an existing file beats a new one; a new one beats a new package.
- Comments: match the neighbours, which are terse. One line in a function body. Package/function docs 3-8 lines, one long block per file at most. Never explain what the code says, never defend a design — that goes in the PR body.
- No layer for data we already have. Check what the server already sends and what the CLI already parses before writing a parser.
- No speculative entries. A filter list, config key or flag with nothing using it today is dead state; leave it out.
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 · 357 lines · 4,765 tokens per session scan A 813d5924a434
praxis-cli CLAUDE.md is an instructions file published in the GitHub repository Facets-cloud/praxis-cli (2 stars, last pushed 2d ago), licensed MIT. It adds 4,765 tokens to every session, about $0.0238 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
no-mistakes AGENTS.md
AGENTS.md instructions for kunchenguid/no-mistakes, covering agents.md and maintaining this file.
trpc-agent-go AGENTS.md
AGENTS.md instructions for trpc-group/trpc-agent-go, covering agents.md, project overview, engineering principles, go design conventions and implementation workflow.
azure-sdk-for-go go-code.instructions.md
Instructions for Azure/azure-sdk-for-go: All code should follow the guidelines from the Azure Go SDK Guidelines. This document is a summary of the most important guidelines to follow when contributing to the Azure Go SDK.
stackql AGENTS.md
Instructions for stackql/stackql, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
goai AGENTS.md
Instructions for zendev-sh/goai, covering agents.md - goai, commands, architecture, key rules and adding providers.
go-agent-skills copilot-instructions.md
Instructions for eduardo-sl/go-agent-skills, covering go agent skills, installation, skills catalog, code quality and architecture & design.