Borrowing it
Nothing to install: this file belongs to SenolIsci/mykg. 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/SenolIsci/mykg/main/.claude/skills/design-architecture/SKILL.mdgit clone --depth 1 https://github.com/SenolIsci/mykgWrote 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/senolisci/mykg/design-architecture)<a href="https://agentmods.dev/skills/senolisci/mykg/design-architecture"><img src="https://agentmods.dev/badge/skills/senolisci/mykg/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/senolisci/mykg/design-architecture"><img src="https://agentmods.dev/badge/skills/senolisci/mykg/design-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.00195 | $0.01953 |
| Opus 5 | $0.00097 | $0.00977 |
| Sonnet 5 | $0.00039 | $0.00391 |
| Haiku 4.5 | $0.00019 | $0.00195 |
Grade A, and why
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 10d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Architecture Skill
This skill performs a structured architecture review by dispatching four specialist subagents in parallel, then
consolidating their findings into a maintained architecture.md document. One of the four subagents is a dedicated
adversarial red-team agent that probes failure paths, invariant bypasses, and silent corruption scenarios that
the structural review agents would not naturally surface.
The goal is not to produce a one-time report — it's to maintain a living architectural record that evolves as the
codebase evolves. The to-do list inside architecture.md becomes the actionable roadmap.
Workflow
Step 1 — Read existing architecture.md (if it exists)
Before spawning subagents, check whether architecture.md already exists in the project root. If it does, read it
so you understand what was previously documented, what to-dos are already tracked, and what changes have already
been logged. This context shapes what the subagents should focus on (new ground vs. follow-up on prior findings).
Step 2 — Spawn four subagents in parallel
Launch all four at once (same message, parallel Agent tool calls). Each subagent is defined in
.claude/agents/ — use the subagent_type parameter to route to each one:
| Subagent | File | subagent_type |
Lens |
|---|---|---|---|
| System Architect | .claude/agents/system-architect.md |
system-architect |
Pipeline structure, orchestration, re-entry |
| Software Architect | .claude/agents/software-architect.md |
software-architect |
Code design, abstractions, invariant enforcement |
| Data Architect | .claude/agents/data-architect.md |
data-architect |
Data models, formats, deduplication, output correctness |
| Adversarial Architect | .claude/agents/adversarial-architect.md |
adversarial-architect |
Failure paths, LLM adversarial output, silent corruption |
Each agent file contains its full focus areas, files to read, questions to answer, and required report format. You do not need to repeat those instructions in the prompt — the agent definitions carry them. Just tell each agent what to do:
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.
- 10d ago First seen · 183 lines · 195 tokens per session scan A 9391d8457842
design-architecture is a skill published in the GitHub repository SenolIsci/mykg (71 stars, last pushed 9d ago), licensed MIT. It adds 195 tokens to every session and 1,953 once invoked, about $0.0010 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
ontology-agent-suite
Orchestrate a hierarchical ontology engineering skill family for a specific domain. Use when the user wants end-to-end planning, team composition, research, ontology construction, validation, and release guidance grounded in competency questions, evidence, reuse-first modeling, and human review gates.
ontology-planning-team
Plan a domain ontology effort by clarifying scope, composing the working team, defining competency questions, and setting risk and approval gates before research begins.
ontology-research-team
Run the research stage for a domain ontology project by collecting primary sources, checking whether the needed data is actually collectible in practice, curating evidence, identifying reuse candidates, and writing research artifacts to the exe folder.
ontology-build-team
Turn research outputs into a domain ontology draft using layered modeling, SKOS-first conceptualization, selective OWL formalization, and explicit modeling decisions tied back to evidence.
ontology-ontology-architect
Design a domain ontology from evidence using layered modeling, stable concept definitions, explicit relations, SKOS-first structure, and selective OWL formalization with recorded modeling decisions.
ontology-technical-plan-writer
Draft or refine a technical planning document template for an ontology project. Use when the user wants a technical proposal, planning brief, or reusable template that connects scope, competency questions, standards reuse, modeling approach, validation, governance, and execution phases without drifting into a…