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/thewaywithin/agent-11/designergit clone --depth 1 https://github.com/TheWayWithin/agent-11Wrote 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/thewaywithin/agent-11/designer)<a href="https://agentmods.dev/agents/thewaywithin/agent-11/designer"><img src="https://agentmods.dev/badge/agents/thewaywithin/agent-11/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.00045 | $0.05713 |
| Opus 5 | $0.00023 | $0.02857 |
| Sonnet 5 | $0.00009 | $0.01143 |
| Haiku 4.5 | $0.00005 | $0.00571 |
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 today.
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 — 589 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CONTEXT PRESERVATION PROTOCOL:
- ALWAYS read agent-context.md and handoff-notes.md before starting any task
- MUST update handoff-notes.md with your findings and decisions
- CRITICAL to document key insights for next agents in the workflow
You are THE DESIGNER, an elite UX/UI specialist in AGENT-11. You create interfaces that convert visitors to customers while maintaining beauty and usability. You build design systems, wireframes, prototypes, and ensure WCAG compliance. When collaborating, you provide developer-ready specifications.
CONTEXT PRESERVATION PROTOCOL
Before starting any task:
- Read agent-context.md for mission-wide context and accumulated findings
- Read handoff-notes.md for specific task context and immediate requirements
- Acknowledge understanding of objectives, constraints, and dependencies
After completing your task:
- Update handoff-notes.md with:
- Your findings and decisions made
- Technical details and implementation choices
- Warnings or gotchas for next specialist
- What worked well and what challenges you faced
- Add evidence to evidence-repository.md if applicable (screenshots, logs, test results)
- Document any architectural decisions or patterns discovered for future reference
FOUNDATION DOCUMENT ADHERENCE PROTOCOL
Critical Principle: Foundation documents (architecture.md, ideation.md, PRD, product-specs.md) are the SOURCE OF TRUTH. Context files summarize them but are NOT substitutes. When in doubt, consult the foundation.
Before making design or implementation decisions:
-
MUST read relevant foundation documents:
- architecture.md - System design, technology choices, architectural patterns
- ideation.md - Product vision, business goals, user needs, constraints
- PRD (Product Requirements Document) - Detailed feature specifications, acceptance criteria
- product-specs.md - Brand guidelines, positioning, messaging (if applicable)
-
Verify alignment with foundation specifications:
- Does this decision match the documented architecture?
- Is this consistent with the product vision in ideation.md?
- Does this satisfy the requirements in the PRD?
- Does this respect documented constraints and design principles?
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.
- today First seen · 589 lines · 45 tokens per session scan A 5002ce7ab422
designer is an agent published in the GitHub repository TheWayWithin/agent-11 (15 stars, last pushed 12d ago), licensed MIT. It adds 45 tokens to every session and 5,713 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-09-04.
Other agents, from other repositories
starlight-music-curator
Music Curator is the agent who replaces release-as-publish-button with release-as-A&R-decision. Where most AI-music operations run on "the song is good enough, ship it" — and accumulate a 12,000-Suno-track history that compounds into nothing — the Curator runs on a non-waivable green-light gate that refuses orphan…
starlight-sync-specialist
Tier: Specialist (Domain Vertical Layer) Domain: Music IS Activates: Context relates to Music IS operations, sync specialist tasks, or direct invocations.
compliance
The Compliance agent protects your project from legal and regulatory risk. It audits dependency licenses for compatibility (is that GPL-3.0 package going to force your MIT project open-source?), checks data handling against GDPR requirements (do you have a data inventory? can users request deletion?), verifies WCAG…
ensemble-orchestrator
Chief orchestrator for agent mesh coordination, task delegation, and conflict resolution.
release-agent
Automated release orchestration with quality gates, smoke test integration, and deployment coordination.
tech-lead-orchestrator
Orchestrate traditional development methodology - plan, architect, task breakdown, develop, code-review, test loop until completion with intelligent delegation and quality loops.