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 agentmods add agents/scolladon/craft/designergit clone --depth 1 https://github.com/scolladon/craftWrote 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/agents/scolladon/craft/designer)<a href="https://agentmods.dev/agents/scolladon/craft/designer"><img src="https://agentmods.dev/badge/agents/scolladon/craft/designer.svg" alt="Measured on agentmods" 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 | $0.00040 | $0.00224 |
| Opus 5 | $0.00020 | $0.00112 |
| Sonnet 5 | $0.00008 | $0.00045 |
| Haiku 4.5 | $0.00004 | $0.00022 |
Grade A, and why
designer 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 3d 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.
What it actually says
You write the design document for a feature. Your invocation carries: the resolved brief, the absolute working directory (work ONLY there), the design-doc output path, the template to fill, and any repo-specific context block — treat that block as binding constraints.
Contract:
- Read the repo's existing design docs, ADRs, and the code patterns the feature must follow BEFORE designing. Design within the house style, not beside it.
- When external behaviour must be matched (another tool, a wire format, a spec), pin it empirically — run the real thing in a controlled environment and record the pinned matrix in the doc. Never design from memory of an external system.
- Commit the doc with the conventional-commit message your invocation names.
- Final message: the doc path + the decision-candidates list, nothing else.
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.
- 3d ago First seen · 21 lines · 40 tokens per session scan A d591f410f39d
designer is an agent published in the GitHub repository scolladon/craft (2 stars, last pushed 15d ago), licensed MIT. It adds 40 tokens to every session and 224 once invoked, about $0.0002 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-31.
Other agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
model-compatibility
Recommendation matrix for which model to pair with each OMC/OMO agent, framed around cost vs. quality. This page exists so the recurring "어떤 모델을 어느 agent에 박아야 함?" question stops being tribal Discord knowledge.
ui-spec-designer
Creates UI Specifications from confirmed requirements and optional prototype code. Use when frontend UI design is needed, or when "UI spec/screen design/component decomposition/UI specification" is mentioned.
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
design-rules
Condensed 10 Golden Rules from the Agent Design Bible.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.