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 NickCrew/Claude-Cortex --skill architectural-analysisgit clone --depth 1 https://github.com/NickCrew/Claude-CortexWrote 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/nickcrew/claude-cortex/architectural-analysis)<a href="https://agentmods.dev/skills/nickcrew/claude-cortex/architectural-analysis"><img src="https://agentmods.dev/badge/skills/nickcrew/claude-cortex/architectural-analysis/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/nickcrew/claude-cortex/architectural-analysis"><img src="https://agentmods.dev/badge/skills/nickcrew/claude-cortex/architectural-analysis.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.00180 | $0.04178 |
| Opus 5.5 | $0.00072 | $0.01671 |
| Sonnet 5.5 | $0.00036 | $0.00836 |
| Haiku 4.5 | $0.00018 | $0.00418 |
Grade A, and why
architectural-analysis 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 1mo 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architectural Analysis
Overview
Produce diagram-first architectural reports for a codebase or a scoped subtree. The primary artifact is a set of mermaid diagrams under docs/architecture/<report-date>/<mode>/, accompanied by markdown reports that resolve every callout to a path:line citation. Every node and every edge in every diagram is grounded in the source — no exceptions outside the explicit synthesized-concept escape hatch.
When to use
Trigger this skill when the user asks for:
- A full architectural snapshot of a codebase ("run a full architectural analysis")
- A scoped diagram of a subsystem ("diagram the data flow through
<path>") - A specific mode by name ("ERD for this app", "where are the failure modes in
<path>", "map the integration points")
Do not trigger for:
- Pure prose explanations with no diagram requirement (use
code-explanation) - New-system design from a blank page (use
system-design) - Single-file walkthroughs (use
diffity-tour)
Modes
Eight analysis modes. Each has its own callout prefix, primary mermaid diagram type, and dedicated reference file in references/.
| Mode | Prefix | Primary diagram | Reference |
|---|---|---|---|
| Information architecture | I- |
graph TD (module hierarchy) or C4 container |
references/mode-information.md |
| Data flow | D- |
flowchart LR + sequenceDiagram per critical path |
references/mode-data-flow.md |
| Integrations | X- |
C4 context boundary | references/mode-integrations.md |
| UI surfaces | U- |
route tree + component graph | references/mode-ui-surfaces.md |
| Interaction patterns | P- |
graph TD per-surface pattern decomposition |
references/mode-interaction-patterns.md |
| Data model | M- |
erDiagram |
references/mode-data-model.md |
| Control flow | C- |
stateDiagram-v2 + sequenceDiagram |
references/mode-control-flow.md |
| Failure modes | F- |
annotated flowchart with error edges | references/mode-failure-modes.md |
Callout IDs are stable across modes — I-12 referenced from a data-flow report points to the same physical node in the IA diagram. The cross-mode index in the synthesis README binds them.
What ships with it
26 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/styles/blueprint/mermaid-dark.json 2.3 KB
- assets/styles/blueprint/mermaid-light.json 2.3 KB
- assets/styles/blueprint/style.css 15 KB
- assets/styles/corporate/mermaid-dark.json 2.3 KB
- assets/styles/corporate/mermaid-light.json 2.3 KB
- assets/styles/corporate/style.css 15 KB
- assets/template.html 7.7 KB
- references/citation-protocol.md 4.7 KB
- references/doc-map.md 2.9 KB
- references/mermaid-conventions.md 7.2 KB
- references/mode-control-flow.md 5.1 KB
- references/mode-data-flow.md 5.0 KB
- references/mode-data-model.md 5.2 KB
- references/mode-failure-modes.md 5.5 KB
- references/mode-information.md 5.1 KB
- references/mode-integrations.md 5.4 KB
- references/mode-interaction-patterns.md 13 KB
- references/mode-ui-surfaces.md 4.9 KB
- references/report-template.md 5.5 KB
- references/subagent-dispatch.md 8.9 KB
- references/synthesis-readme.md 5.6 KB
- references/verification-protocol.md 4.9 KB
- scripts/compile-html.sh 9.9 KB runs code
- scripts/compile-pdf.sh 5.0 KB runs code
- scripts/render.sh 5.3 KB runs code
- scripts/verify-citations.sh 2.4 KB runs code
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.
- 1mo ago First seen · 261 lines · 180 tokens per session scan A 4104d3f58332
architectural-analysis is a skill published in the GitHub repository NickCrew/Claude-Cortex (56 stars, last pushed 3mo ago), licensed MIT. It adds 180 tokens to every session and 4,178 once invoked, about $0.0007 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-09-03.
Other skills, from other repositories
create-stories
Break one epic into implementable stories embedding TR-ID, ADR guidance, acceptance criteria. Reads the control manifest. After /create-epics.
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
quick-design
Lightweight spec for small changes — tuning adjustments, minor mechanics. Embeds directly into stories; skips full GDD.
playtest-report
Structured playtest report template, or turn existing playtest notes into structured feedback.
test-setup
Scaffold the test framework and CI — tests/ directory, engine test runner, GitHub Actions workflow. Once, before the first sprint.
qa-plan
QA test plan for a sprint — classifies stories by Logic/Integration/Visual/UI, covers automated tests, manual cases, smoke scope.