aiagent: Skill for Claude Code

.claude/skills/design-review/SKILL.md

design-review is a skill for Claude Code from drujensen/aiagent. It costs 52 tokens per session (509 once invoked), scanned A, original, MIT.

A workflow that has an architect create a technical design and an architecture reviewer assess it against maintainability, reliability, scalability, usability, security, and quality. The design is revised when the review finds important problems.

In plain words
What is it for?
Use it to create and scrutinise designs for changes in a Go project, including file placement, interfaces, and relevant API decisions.
Why use it?
It exposes architectural weaknesses before implementation begins and gives the design a defined review-and-revise process.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

This is drujensen/aiagent's own configuration. It tells Claude Code how to work on aiagent itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything aiagent configures →

Reuse

Borrowing it

Nothing to install: this file belongs to drujensen/aiagent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/drujensen/aiagent/main/.claude/skills/design-review/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/drujensen/aiagent

Made for: Claude Code.

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 design-review

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/drujensen/aiagent/design-review"><img src="https://agentmods.dev/badge/skills/drujensen/aiagent/design-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 509 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.00052 $0.00509
Opus 5.5 $0.00021 $0.00204
Sonnet 5.5 $0.00010 $0.00102
Haiku 4.5 $0.00005 $0.00051

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

Security

Grade A, and why

design-review 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 4d 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.

.claude/skills/design-review/SKILL.md · 51 lines

What it actually says

Design Review

Design and review the following:

Instructions

You are orchestrating an Architecture Design Review cycle for the aiagent project.

Phase 1: Design

  1. Use the Agent tool with subagent_type: "architect" to design the solution
  2. Pass it the story description (and the full story-refiner output if available)
  3. The architect will:
    • Read the relevant codebase before designing
    • Default to maintaining existing DDD patterns
    • Produce a design document with file paths, interface definitions, and RESTful API standards where applicable

Phase 2: Review 3. Use the Agent tool with subagent_type: "architect-reviewer" to review the design 4. Pass the architect's full design document to the reviewer 5. The reviewer will score against the 6 pillars (Maintainability, Reliability, Scalability, Usability, Security, Quality)

Phase 3: Iterate 6. If overall score >= 8/10 (APPROVED): Report the approved design and scores 7. If overall score < 8/10 (REVISE):

  • Extract the specific Critical Issues from the reviewer
  • Send those issues back to the architect via Agent tool
  • Ask the architect to revise the design addressing those issues
  • Re-review with the architect-reviewer
  • Repeat until APPROVED or 3 iterations maximum

Phase 4: Report 8. Present:

  • Approved design document (full text)
  • Final pillar scores table
  • Iteration count and what changed between iterations
  • Note: this design is the input to /adlc implementation planning

Important

  • Maximum 3 review iterations to prevent infinite loops
  • If not approved after 3 iterations, present the work with remaining issues flagged
  • The architect DESIGNS; the architect-reviewer only READS and SCORES
  • The approved design document should be saved — it is passed verbatim to the planner
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. 4d ago First seen · 51 lines · 52 tokens per session scan A 59c6f8b3ca24

Subscribe to this mod's changes

design-review is a skill published in the GitHub repository drujensen/aiagent (5 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 509 once invoked, about $0.0002 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-10-03.

Related

Other skills, from other repositories

autoreview

Structured code review through the shared OpenClaw agent-skills installation.

openclaw/clawhub · 17 tokens

omh-code-review

This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 48 tokens

revdiff-plan

Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…

umputun/revdiff · 84 tokens

asplos-writing-style

Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…

brycewang-stanford/Awesome-Journal-Skills · 65 tokens

explore-unknowns

Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…

dzhng/skills · 162 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens