architect-design

architect-design is a skill for Claude Code, Codex from zookanalytics/gc-toolkit. It costs 0 tokens per session (1,036 once invoked), scanned A, original, MIT.

A design method for deciding the structure of a software change before writing code. It reads the request and existing architecture, asks questions about important constraints, and records decisions in an architecture document.

In plain words
What is it for?
It is for turning a product requirement, rough idea, or existing codebase into documented architectural decisions and component boundaries.
Why use it?
It reduces unclear boundaries and conflicting assumptions when several parts of a system must work together.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It is for turning a product requirement, rough idea, or existing codebase into documented architectural decisions and component boundaries.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zookanalytics/gc-toolkit/architect-design
Install

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.

Any agent
npx skills add zookanalytics/gc-toolkit --skill architect-design
Clone the repo
git clone --depth 1 https://github.com/zookanalytics/gc-toolkit

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for architect-design

README.md
[![agentmods](https://agentmods.dev/badge/skills/zookanalytics/gc-toolkit/architect-design/github.svg)](https://agentmods.dev/skills/zookanalytics/gc-toolkit/architect-design)
Your own site
<a href="https://agentmods.dev/skills/zookanalytics/gc-toolkit/architect-design"><img src="https://agentmods.dev/badge/skills/zookanalytics/gc-toolkit/architect-design/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.

agentmods 80×15 button for architect-design

Your own site · 80×15
<a href="https://agentmods.dev/skills/zookanalytics/gc-toolkit/architect-design"><img src="https://agentmods.dev/badge/skills/zookanalytics/gc-toolkit/architect-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,036 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01036
Opus 5.5 $0.00000 $0.00414
Sonnet 5.5 $0.00000 $0.00207
Haiku 4.5 $0.00000 $0.00104

Measured 29d ago against content hash dfe41ee9fc3d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

architect-design 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 29d 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.

specs/tk-ae96t/reference/architect-design.skill.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

architect-design

A method-skill of the architect persona (see the architect identity skill). Self-contained: it carries its own method and declares the files it reads/writes. Engage it whenever the work is to design — as a mol step on its own, or when a session has worn the architect identity. Settling structure before the code is written.

Files I read and write

  • Read: the PRD / change request / idea being designed; the existing docs/architecture.md (the current shape, if any); the code regions whose boundaries the change touches.
  • Write (advisory): docs/architecture.md — append/update the decisions and the shape. Advisory: I keep it current; nothing enforces it.

The stance

Elicitation is the value; drafting is the anti-pattern. A finished design produced from two quick questions is the failure mode, not the win. Gather context and ask the questions that change the answer before committing structure. Surface trade-offs, not verdicts.

Method

  1. Read the inputs to know the job. Which are you in?
    • a spec/PRD to turn into structure;
    • a raw idea to shape;
    • an existing codebase to derive the shape from (ratify the conventions already there before inventing new ones);
    • a change to an existing system (inherit its current invariants as constraints — treat already-settled decisions as read-only unless the change is explicitly to revisit them).
  2. Elicit. Ask the clarifying questions whose answers would change the structure — non-functional requirements (scale, latency, consistency, failure modes), the boundaries that already exist, what must stay reversible. Don't proceed past a genuinely open question; surface it.
  3. Pin only the invariants — the inclusion test. Fix a decision in the architecture only when all three hold:
    • two parts one level down, built independently, could choose incompatibly (paradigm, boundary & dependency rules, how state is mutated, who owns shared data, the contract between units), and
    • the call is non-obvious, and
    • it's a real trade-off (not a default everyone would reach anyway).

Read the full file on GitHub · 87 lines

Changes

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.

  1. 29d ago First seen · 87 lines · 0 tokens per session scan A dfe41ee9fc3d

Subscribe to this mod's changes

architect-design is a skill published in the GitHub repository zookanalytics/gc-toolkit (5 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,036 tokens. 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-19.