Borrowing it
Nothing to install: this file belongs to aget-framework/aget. 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/aget-framework/aget/main/.claude/skills/aget-design-architecture/SKILL.mdgit clone --depth 1 https://github.com/aget-framework/agetWrote 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/aget-framework/aget/aget-design-architecture)<a href="https://agentmods.dev/skills/aget-framework/aget/aget-design-architecture"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-design-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/aget-framework/aget/aget-design-architecture"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-design-architecture.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.00012 | $0.00582 |
| Opus 5 | $0.00006 | $0.00291 |
| Sonnet 5 | $0.00002 | $0.00116 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade A, and why
aget-design-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 9d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aget-design-architecture
Design system architecture including components, relationships, and patterns. Addresses quality attributes and produces architectural artifacts.
Instructions
When this skill is invoked:
-
Understand Requirements
- Gather functional requirements
- Identify quality attributes (scalability, reliability, security, etc.)
- Note constraints (technology, budget, timeline)
-
Decompose the System
- Identify logical components
- Define responsibilities (single responsibility)
- Establish boundaries
-
Select Patterns
- Choose appropriate architectural patterns:
- Layered, Microservices, Event-Driven, etc.
- Match patterns to requirements and constraints
- Choose appropriate architectural patterns:
-
Define Relationships
- Document interfaces between components
- Specify communication protocols
- Map dependencies
-
Address Quality Attributes
- Scalability: How system grows
- Reliability: How system handles failure
- Security: How system protects assets
Output Format
## Architecture Design: [System Name]
### Overview
[2-3 sentence description of the architecture]
### Components
| Component | Responsibility | Interface |
|-----------|---------------|-----------|
| [Name] | [What it does] | [API/Events/etc.] |
### Architecture Diagram
┌─────────────┐ ┌─────────────┐ │ Component A │────▶│ Component B │ └─────────────┘ └─────────────┘ │ ▼ ┌─────────────┐ │ Component C │ └─────────────┘
### Patterns Applied
| Pattern | Rationale |
|---------|-----------|
| [Pattern] | [Why chosen] |
### Quality Attributes
| Attribute | Approach |
|-----------|----------|
| Scalability | [How addressed] |
| Reliability | [How addressed] |
| Security | [How addressed] |
### Dependencies
A → B (sync API) B → C (async events)
### Risks & Trade-offs
- [Trade-off 1]: [What was traded for what]
Constraints
- C1: NEVER propose architecture without understanding requirements — architecture serves requirements
- C2: NEVER introduce unnecessary complexity — simplest solution meeting requirements preferred
- C3: NEVER ignore non-functional requirements — quality attributes are architectural drivers
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.
- 9d ago First seen · 109 lines · 12 tokens per session scan A 880de01c057d
aget-design-architecture is a skill published in the GitHub repository aget-framework/aget (11 stars, last pushed today), licensed Apache-2.0. It adds 12 tokens to every session and 582 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
aget-close-project
Close a PROJECTPLAN with verifiable-assertion gate (V-tests + commits + retrospective), deferred-surface scan for next-plan handoff, and status transition (ACTIVE → COMPLETE / CLOSED / ABANDONED / SUPERSEDED). Strict counterpart to /aget-create-project (D71 Layer 2). Closes asymmetric verb-pair gap at PROJECTPLAN…
aget-release-critique
Adversarial review with the Critic perspective of the Release Delivery Triad (L818). Dual-mandate: spec coverage audit + deep bug finding.
aget-release-audit-specs
Audit specifications with the Spec Auditor perspective of the Release Delivery Triad (L818). Coverage and consistency mode.
aget-file-issue
File issues with L520 governance compliance.
aget-release-build
Execute gate deliverables with the Builder perspective of the Release Delivery Triad (L818). Speed-optimized execution mode.
aget-propose-actions
Propose ranked next-best actions with evidence grounding, time budgets, and execute-all default. Formalizes the fleet's highest-frequency interaction pattern.