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/cenconq25/claude-code-app-studio/create-architecturenpx skills add cenconq25/claude-code-app-studio --skill create-architecturegit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote 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/cenconq25/claude-code-app-studio/create-architecture)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/create-architecture"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/create-architecture.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.00069 | $0.02751 |
| Opus 5 | $0.00034 | $0.01375 |
| Sonnet 5 | $0.00014 | $0.00550 |
| Haiku 4.5 | $0.00007 | $0.00275 |
Grade A, and why
create-architecture 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 yesterday.
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 — 411 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Architecture
Produces the project's master architecture document — the technical blueprint that ADRs slot into. Without this, ADRs are scattered points without a structure.
Output: docs/architecture/architecture.md
Purpose / When to Run
Run when:
- All MVP PRDs are individually approved and
/review-all-prdsreturned PASS - The team is ready to commit to top-level structure before writing ADRs
Distinct from /architecture-decision (single decision) — this skill creates the frame that decisions hang on, plus the list of which ADRs are required.
Inputs
- All
design/prd/*.md design/systems-index.mddesign/concept.md- Existing
docs/architecture/ADR-*.md(if any — typically retrofit) docs/framework-reference/<framework>/.claude/docs/technical-preferences.md
Outputs
docs/architecture/architecture.md- A "Required ADRs" list inside that doc
- Optional initial
docs/architecture/architecture-registry.yamlskeleton
Phase 1: Pre-checks
- Confirm framework is pinned (
technical-preferences.mdnot[TO BE CONFIGURED]) - Confirm at least 80% of MVP PRDs are APPROVED in
design/systems-index.md - If
/review-all-prdshas not been run or returned PASS, warn: "Architecture without holistic PRD review can codify contradictions. Consider running/review-all-prdsfirst." Allow proceed anyway.
If docs/architecture/architecture.md exists, ask:
Refresh sections (incremental)— re-author specific sectionsRebuild from scratch (back up first)— full new draftCancel
Phase 2: Read All Context
This skill is read-heavy. Hold in context:
- All PRDs
- Concept doc
- Systems index
- Existing ADRs (to integrate, not duplicate)
- Framework reference: VERSION.md, conventions.md, breaking-changes.md
- Technical preferences
Note knowledge-cutoff risk for the pinned framework — if HIGH, flag in the doc header that decisions in tricky domains must consult breaking-changes.md.
Phase 3: Skeleton
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.
- yesterday First seen · 411 lines · 69 tokens per session scan A 152a3a0f2369
create-architecture is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 69 tokens to every session and 2,751 once invoked, about $0.0003 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-09-03.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…