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 skills add jeet129/praxis --skill architecture-documentationgit 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-documentation)<a href="https://agentmods.dev/skills/jeet129/praxis/architecture-documentation"><img src="https://agentmods.dev/badge/skills/jeet129/praxis/architecture-documentation.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 8 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00152 | $0.02927 |
| Opus 5 | $0.00076 | $0.01463 |
| Sonnet 5 | $0.00030 | $0.00585 |
| Haiku 4.5 | $0.00015 | $0.00293 |
Grade A, and why
architecture-documentation 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 7d 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 — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Documentation
capability: maintenance
domain: cross-cutting
state: active
dependencies:
- architecture-pattern-selection
- adr-decision-records
- codebase-comprehension
- api-design
- data-modeling
triggers:
- "establishing initial architecture documentation for a new project"
- "significant architecture change shipping (new service, new boundary, new pattern)"
- "new joiner onboarding (architecture-docs is their first read)"
- "discovering documentation drift (docs disagree with reality)"
- "monthly reconciliation cadence"
- "preparing architecture review or audit"
outputs:
- C4 context diagram (Level 1)
- C4 container diagram (Level 2)
- C4 component diagrams (Level 3; per container as needed)
- ADR archive (chronological)
- architecture overview document (the human-readable narrative)
- trust-boundary + data-flow diagrams
- decision log index (ADR titles + dates + status)
consumers:
- solution-architect (primary author + reconciler)
- lead-developer (consumes when planning slices)
- architecture-challenger (reads to challenge from a current view)
- new-joiner onboarding (their starting point)
- impact-analysis (consumes the system map)
- tech-writer (assists with prose; integrates with `technical-documentation`)
references: []
The discipline that keeps architecture knowable. Documentation that has drifted from the deployed system is worse than no documentation — it confidently misleads. This skill is the practice of maintaining a small set of high-leverage architecture artifacts so they reflect what's actually built, today.
The principle: architecture docs are a living artifact. The cadence of reconciliation determines whether they're an asset or a liability.
When this skill fires
- Establishing initial architecture documentation for a new project.
- Significant architecture change shipping — new service, new boundary, new pattern.
- New joiner onboarding — architecture docs are their starting read.
- Documentation drift discovered (docs disagree with reality).
- Monthly reconciliation cadence.
- Preparing for architecture review or audit.
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.
- 7d ago First seen · 288 lines · 152 tokens per session scan A 2ebb929ea83f
architecture-documentation is a skill published in the GitHub repository jeet129/praxis (7 stars, last pushed 3d ago), licensed MIT. It adds 152 tokens to every session and 2,927 once invoked, about $0.0008 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-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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…