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 cenconq25/claude-code-app-studio --skill architecture-decisiongit 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/architecture-decision)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/architecture-decision"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/architecture-decision.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.00062 | $0.02958 |
| Opus 5 | $0.00031 | $0.01479 |
| Sonnet 5 | $0.00012 | $0.00592 |
| Haiku 4.5 | $0.00006 | $0.00296 |
Grade A, and why
architecture-decision 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 8d 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 — 408 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Decision
ADRs are the durable memory of why the architecture is shaped a given way. This skill captures one decision, anchored to PRD requirements, with the framework's knowledge-cutoff risk explicitly tracked.
Output: docs/architecture/ADR-NNNN-<slug>.md
Phase 0: Argument Parsing & Mode
Resolve review mode:
--reviewflag if present- Else
production/review-mode.txt - Else default
lean
If the argument starts with retrofit <path>, enter retrofit mode:
- Read the existing ADR
- Identify which standard sections are present:
## Status— CRITICAL if missing (/story-readinesscannot validate)## ADR Dependencies— HIGH (sequencing risk)## Framework Compatibility— HIGH (knowledge-cutoff risk untracked)## PRD Requirements Addressed— HIGH (traceability lost)
- Print the gap report
- Ask: "Add the [N] missing sections without modifying existing content?"
- If yes:
- For Status: ask the user (Proposed / Accepted / Deprecated / Superseded)
- For ADR Dependencies: ask Depends On / Enables / Blocks (each can be "None")
- For Framework Compatibility: read framework reference docs and generate the table; ask user to confirm domain
- For PRD Requirements Addressed: ask which PRDs and which requirements
- Append using Edit tool — never modify existing sections
- Done; suggest re-running
/architecture-reviewto validate.
If no argument or title:
"What technical decision are you documenting? Provide a short slug (e.g.,
state-management,navigation-library,auth-token-storage)."
Then proceed to Phase 1.
Phase 1: Load Framework Context
Always run before drafting. The model has knowledge cutoffs; the framework reference docs are the source of truth.
- Read
.claude/docs/technical-preferences.mdto identify the framework + version - If
[TO BE CONFIGURED]: stop and recommend/setup-framework - Identify the domain of this decision from the title:
- State management
- Navigation
- Networking / API client
- Persistence (local DB, secure storage)
- Auth (token storage, refresh)
- Push notifications
- Background tasks
- Analytics / instrumentation
- Feature flags / remote config
- Error reporting
- i18n
- Theming / dark mode
- Build system / CI
- Testing strategy
- Code organization / module boundaries
- In-app purchase / subscriptions
- Deep links / universal links
- Biometrics / secure enclave
- Camera / media / AVFoundation / CameraX
- Maps / location
- Read
docs/framework-reference/<framework>/conventions.md - Read
docs/framework-reference/<framework>/breaking-changes.md— flag any post-cutoff entries in this domain - Read
docs/framework-reference/<framework>/VERSION.md— note the risk level
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.
- 8d ago First seen · 408 lines · 62 tokens per session scan A 9025cae8ff3f
architecture-decision is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 62 tokens to every session and 2,958 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-08-30.
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…