agentmods.dev

design

design is a skill for Claude Code, Codex from drujensen/aiagent. It costs 45 tokens per session (630 once invoked), scanned A, original, MIT.

A workflow for turning research or a request into a technical design that follows the project's architecture rules. It defines the entities, interfaces, services, files, and reuse decisions needed for the change.

In plain words
What is it for?
Use it to design changes for a Go Domain-Driven Design project, including where components belong and how they should connect.
Why use it?
It gives implementation a clear structure and helps prevent new code from breaking layer boundaries or duplicating existing features.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions CLAUDE.md; mentions AGENTS.md.

not rated 5repo 2mo ago A scan 45 tokens original MIT

Good fit Use it to design changes for a Go Domain-Driven Design project, including where components belong and how they should connect.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/drujensen/aiagent/design
View source ↗ drujensen/aiagent
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 drujensen/aiagent --skill design
Clone the repo
git clone --depth 1 https://github.com/drujensen/aiagent

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 design

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/drujensen/aiagent/design"><img src="https://agentmods.dev/badge/skills/drujensen/aiagent/design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 630 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.00045 $0.00630
Opus 5.5 $0.00018 $0.00252
Sonnet 5.5 $0.00009 $0.00126
Haiku 4.5 $0.00005 $0.00063

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

Security

Grade A, and why

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

skills/design/SKILL.md · 35 lines

How it starts

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

Design

You have been activated to produce a technical design from a prior research findings summary (or from the request directly, if no research step preceded this one). Your job is to decide the shape of the solution, not to implement it.

Instructions

  1. Enforce project conventions first. Before proposing anything, read the repository's CLAUDE.md (root) and any relevant AGENTS.md files for the directories you expect to touch. Every design decision you make must be consistent with what those files say - constructor naming (NewXxx), interface naming (...Repository/...Service), the context.Context-first method signature convention, struct tag conventions (json:"..." bson:"..."), and the strict rule that internal/domain/ code never imports internal/impl/.
  2. Reuse before inventing. Identify existing entities, interfaces, services, or tools that already do something close to what's needed. Prefer extending or composing over duplicating. State explicitly what you are reusing and what is genuinely new.
  3. Define the shape of the change:
    • New or modified entities (internal/domain/entities/)
    • New or modified interfaces (internal/domain/interfaces/)
    • New or modified services (internal/domain/services/)
    • New or modified implementations (internal/impl/...), noting that JSON and MongoDB repositories must both be updated when a repository interface changes
    • Any new tool, following the existing entities.Tool interface and ToolFactoryEntry registration pattern
  4. Call out concurrency and storage-duality implications. If the change touches a repository, state how it will stay safe under concurrent access (the existing repositories use sync.RWMutex with a deep-copy-on-read/write contract) and how JSON and Mongo storage will be kept consistent.
  5. Keep it minimal. Do not propose abstractions, patterns, or generality beyond what the request actually needs. Three similar lines of code is preferable to a premature abstraction, per this project's stated engineering principles.

Read the full file on GitHub · 35 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. 4d ago First seen · 35 lines · 45 tokens per session scan A 7f10ac9a3938

Subscribe to this mod's changes

design is a skill published in the GitHub repository drujensen/aiagent (5 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 630 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.

GoLanguagesPlanning
Related

Other skills, from other repositories

golang-testing

Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.

affaan-m/ECC · 37 tokens

golang-patterns

Go-specific design patterns and best practices including functional options, small interfaces, dependency injection, concurrency patterns, error handling, and package organization. Use when working with Go code to apply idiomatic Go patterns.

affaan-m/ECC · 45 tokens

ast-grep

Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search. This skill should be used when users ask to search for…

JanDeDobbeleer/oh-my-posh · 80 tokens

golang-testing

Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…

samber/cc-skills-golang · 115 tokens

golang-samber-oops

Structured error handling in Golang with samber/oops — error builders, stack traces, error codes, error context, error wrapping, error attributes, user-facing vs developer messages, panic recovery, and logger integration. Apply when using or adopting samber/oops, or when the codebase already imports…

samber/cc-skills-golang · 74 tokens

golang-uber-fx

Golang application framework using uber-go/fx — fx.New, fx.Provide, fx.Invoke, fx.Module, fx.Lifecycle hooks, fx.Annotate (name/group/As), fx.Decorate, fx.Supply, fx.Replace, fx.WithLogger, and signal-aware Run(). Apply when using or adopting uber-go/fx, when the codebase imports go.uber.org/fx, or when wiring…

samber/cc-skills-golang · 122 tokens