Borrowing it
Nothing to install: this file belongs to victoriacity/openakari. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/victoriacity/openakari/main/.claude/skills/architecture/SKILL.mdgit clone --depth 1 https://github.com/victoriacity/openakariWrote 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/victoriacity/openakari/architecture)<a href="https://agentmods.dev/skills/victoriacity/openakari/architecture"><img src="https://agentmods.dev/badge/skills/victoriacity/openakari/architecture/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/victoriacity/openakari/architecture"><img src="https://agentmods.dev/badge/skills/victoriacity/openakari/architecture.svg" alt="Reviewed on agentmods" width="80" 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.00024 | $0.03383 |
| Opus 5.5 | $0.00010 | $0.01353 |
| Sonnet 5.5 | $0.00005 | $0.00677 |
| Haiku 4.5 | $0.00002 | $0.00338 |
Grade A, and why
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 2mo 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 — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/architecture
Analyze and evolve the akari infrastructure — from targeted refactoring of a single file to cross-cutting architectural redesign. This skill operates at four levels:
- Auto (autonomous diagnosis) — detect, prioritize, and implement architecture improvements autonomously
- Refactor (structural, behavior-preserving) — split files, extract modules, reduce coupling
- Map (analytical, read-only) — trace agent types, data flows, module dependencies, system boundaries
- Redesign (behavioral, architectural) — propose and implement changes to how components interact, what agents exist, how data flows
The argument determines the mode:
| Argument | Mode | Example |
|---|---|---|
auto or empty |
Autonomous diagnosis | /architecture auto or /architecture |
| File path or module name | Refactor | /architecture chat.ts |
scan |
Refactor scan | /architecture scan |
map or map <subsystem> |
Architectural map | /architecture map agents |
| Anything else | Redesign | /architecture unify chat and autofix agents |
When to use
- vs
/simplify: simplify removes; architecture restructures. - vs
/gravity: gravity adds capabilities; architecture reorganizes existing ones. - vs
/design: design is for experiment methodology; architecture is for infrastructure code.
Mode: Auto (Autonomous Diagnosis and Improvement)
When invoked without specific instructions (/architecture or /architecture auto), autonomously diagnose the infrastructure's architectural health and implement improvements following the hierarchy: safety > clarity > efficiency.
Step 1: Scan for architectural issues
Survey the entire infra/ directory structure for issues across five dimensions:
- File size violations — files exceeding ~150 lines that mix concerns
- Duplication — repeated code patterns across files (use
Grepfor common function signatures, error patterns, config handling) - Coupling — modules with excessive cross-dependencies or circular imports (trace imports)
- Clarity gaps — missing documentation, unclear interfaces, inconsistent naming
- Type safety violations — any files that would fail
tsc --noEmitor haveanytypes where specific types belong
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.
- 2mo ago First seen · 311 lines · 24 tokens per session scan A 01c44c10d069
architecture is a skill published in the GitHub repository victoriacity/openakari (47 stars, last pushed 7mo ago), licensed MIT. It adds 24 tokens to every session and 3,383 once invoked, about $0.0001 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…