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 commands/jeet129/praxis/architectgit clone --depth 1 https://github.com/jeet129/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/jeet129/praxis/architect)<a href="https://agentmods.dev/commands/jeet129/praxis/architect"><img src="https://agentmods.dev/badge/commands/jeet129/praxis/architect.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.00019 | $0.00386 |
| Opus 5 | $0.00010 | $0.00193 |
| Sonnet 5 | $0.00004 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
architect 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
Start Phase B. Activate the Solution Architect agent. Run the architecture skill sequence:
domain-discovery(if not already done in Phase A) — bounded contexts, ubiquitous language.architecture-pattern-selection— monolith vs services vs event-driven; data stores; sync vs async.api-design— OpenAPI spec scaffold; versioning strategy.data-modeling— schema + multi-tenant scoping if applicable.resilience-patterns— circuit breaker, retry, bulkhead per NFR availability target.distributed-systems-patterns(if distributed) — CAP/PACELC + idempotency + saga/outbox.multi-tenancy(if is_multi_tenant) — silo / pool / bridge model.threat-modeling— STRIDE + trust boundaries + data flows.project-phasing— phased roadmap.
Output ADRs to .project/decision/; diagrams to .project/working/architecture/.
Then spawn Architecture Challenger. Run all 5 sub-personas (scale / security / cost / operations / reliability). Produce challenge report (MANDATORY).
For each Challenger finding:
- ACCEPT → SA updates the design.
- OVERRIDE → SA writes ADR with rationale; triggers
challenger_objection_overridegate.
Prep the architecture_sign_off gate evidence pack: architecture decision + ADR + C4 diagrams + challenge report (MANDATORY) + phased roadmap. Show me before approving.
Common rationalizations to ignore:
- "The architecture is obvious." → the Challenger finds what the SA missed. Run it.
- "Threat modeling at code time is enough." → STRIDE at architecture time catches what OWASP scans can't.
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 · 30 lines · 19 tokens per session scan A a96d907e0730
architect is a command published in the GitHub repository jeet129/praxis (7 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 386 once invoked, about $0.0001 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.