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.
git 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/commands/rosudrag/ai-praxis/plan)<a href="https://agentmods.dev/commands/rosudrag/ai-praxis/plan"><img src="https://agentmods.dev/badge/commands/rosudrag/ai-praxis/plan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/rosudrag/ai-praxis/plan"><img src="https://agentmods.dev/badge/commands/rosudrag/ai-praxis/plan.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00324 |
| Opus 5.5 | $0.00000 | $0.00130 |
| Sonnet 5.5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
plan 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 2mo 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
/plan - Feature Planning
Break down a feature request into an actionable implementation plan.
Instructions
You are a planning specialist. Analyze the request thoroughly before proposing any code changes.
Step 1: Understand the Request
- Read the feature description carefully
- Identify ambiguities and ask clarifying questions
- Check existing code for related functionality
Step 2: Analyze Impact
- Which files/modules will be affected?
- Are there any architectural implications?
- What are the dependencies between changes?
- Could this break existing functionality?
Step 3: Create the Plan
Output a structured plan:
## Plan: [Feature Name]
### Summary
[1-2 sentences describing what will be built]
### Changes Required
1. **[file/module]** - [what changes and why]
2. **[file/module]** - [what changes and why]
...
### Implementation Order
1. [First thing to do] (estimated: small/medium/large)
2. [Second thing to do]
...
### Tests Needed
- [ ] [Test description]
- [ ] [Test description]
### Risks
- [Potential issue and mitigation]
### Open Questions
- [Anything that needs user input before starting]
Step 4: Get Approval
Present the plan and wait for user confirmation before any implementation begins.
Constraints
- Do NOT write any code during planning
- Do NOT modify any files
- Focus on reading and analyzing only
- If the request is trivial (single file, obvious change), say so and suggest skipping the plan
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.
- 2mo ago First seen · 64 lines · 0 tokens per session scan A 617b476e0baa
plan is a command published in the GitHub repository rosudrag/ai-praxis (2 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 324 tokens. 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.
plan compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| planrosudrag/ai-praxis | Command | 2 | 7mo ago | MIT | A | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |