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 liza-mas/liza --skill architecture-planninggit clone --depth 1 https://github.com/liza-mas/lizaWrote 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/liza-mas/liza/architecture-planning)<a href="https://agentmods.dev/skills/liza-mas/liza/architecture-planning"><img src="https://agentmods.dev/badge/skills/liza-mas/liza/architecture-planning/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/liza-mas/liza/architecture-planning"><img src="https://agentmods.dev/badge/skills/liza-mas/liza/architecture-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00016 | $0.01950 |
| Opus 5 | $0.00008 | $0.00975 |
| Sonnet 5 | $0.00003 | $0.00390 |
| Haiku 4.5 | $0.00002 | $0.00195 |
Grade A, and why
architecture-planning 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 12d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Objective
Consolidate approved upstream deliverables into a cohesive architectural plan that downstream code-planners can implement independently.
Output: a git-tracked architecture document (specs/arch-plan/<goal-slug>/<timestamp>-<task-id>.md) plus
structured output[] entries, one per code-planning scope. Each output entry becomes a
code-planning child task — the code-planner reads the architecture document and its scope entry,
the goal spec, and referenced material. Write accordingly: the arch doc should be self-contained
for structural decisions, leaving behavioral detail to the spec.
The architect bridges what (spec) and how (code plan). Spec says what to build; the architect says where each piece goes and how pieces connect. Code-planners turn each scope into implementation steps.
Trigger
- Orchestrator creates an architecture task (§BRAND_NAME_TITLE§ mode)
- User asks to plan architecture for a feature or change (Pairing mode)
- Implementation planning requires structural decisions before code-planning
Inputs
Your task provides:
- A goal spec (
spec_ref) — what must be built - Parent task context — upstream deliverables being consolidated (many-to-one fan-in)
- An output mechanism —
set-task-outputfor each code-planning scope
Scope discipline:
- Upfront: Read goal spec + parent task deliverables + explore relevant codebase areas
- On demand: Broader exploration only when structural questions require it
- Declare what you read and why in References
Output Format
Architecture Plan format at the task-specified path.
Protocol
1. Consolidate
Read and synthesize all inputs before making any structural decisions.
- Read the goal spec — the authoritative source for what must be built
- Read all parent task deliverables (descriptions, outputs, referenced specs/plans)
- Synthesize scope: what is the full extent of what must be built?
- Identify:
- Overlaps — parent deliverables that touch the same area
- Gaps — scope in the goal spec not covered by any parent deliverable
- Conflicts — parent deliverables that make incompatible assumptions
What ships with it
1 file 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.
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.
- 12d ago First seen · 174 lines · 16 tokens per session scan A d97c6790a9a4
architecture-planning is a skill published in the GitHub repository liza-mas/liza (384 stars, last pushed 3d ago), licensed Apache-2.0. It adds 16 tokens to every session and 1,950 once invoked, about $0.0001 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…
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…
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…