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 skills/jeet129/praxis/architecture-pattern-selectionnpx skills add jeet129/praxis --skill architecture-pattern-selectiongit 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/skills/jeet129/praxis/architecture-pattern-selection)<a href="https://agentmods.dev/skills/jeet129/praxis/architecture-pattern-selection"><img src="https://agentmods.dev/badge/skills/jeet129/praxis/architecture-pattern-selection.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.00130 | $0.02771 |
| Opus 5 | $0.00065 | $0.01385 |
| Sonnet 5 | $0.00026 | $0.00554 |
| Haiku 4.5 | $0.00013 | $0.00277 |
Grade A, and why
architecture-pattern-selection 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Pattern Selection
capability: architecture
domain: cross-cutting
state: active
dependencies:
- requirements-elicitation
- nfr-definition
- product-discovery
triggers:
- "entering architecture phase"
- "selecting macro-architecture pattern"
- "a slice requires architectural extension or change"
- "evaluating whether to extract a microservice"
- "deciding between monolith vs distributed"
outputs:
- architecture decision (chosen pattern + rationale)
- C4 component diagram (context + container + component views)
- rejected alternatives with rationale
- ADR
- input to Architecture Challenger (which runs sub-personas against this)
consumers:
- solution-architect (primary author)
- architecture-challenger (consumes for adversarial review)
- delivery-planner (uses chosen pattern to calibrate workflow)
- all developers (consume the architecture as design context)
- architecture-documentation (keeps living docs)
references: []
The single most consequential decision in a project. Get the macro-architecture right and the rest of the design is constrained productively; get it wrong and you spend the project fighting the architecture.
This skill's default bias is simplicity. The right architecture is the simplest one that meets the NFRs. A modular monolith almost always beats microservices for projects under ~10 engineers; serverless beats containers for spiky workloads with no warm-state needs; event-driven beats request/response when temporal decoupling is the actual requirement.
When this skill fires
- A new project transitions from requirements to design. SA runs this skill.
- A slice within an existing project introduces a workload the existing architecture can't handle gracefully (e.g., adding a real-time matching engine to a request/response service). The skill is run scoped to that workload's architectural needs.
- An architecture review (Steward + Curator) revisits the choice based on factory-evaluation signals.
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 · 200 lines · 130 tokens per session scan A 08ceadfd586d
architecture-pattern-selection is a skill published in the GitHub repository jeet129/praxis (7 stars, last pushed yesterday), licensed MIT. It adds 130 tokens to every session and 2,771 once invoked, about $0.0006 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…