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/pedromosquera/squadai/designergit clone --depth 1 https://github.com/PedroMosquera/squadaiWrote 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/pedromosquera/squadai/designer)<a href="https://agentmods.dev/agents/pedromosquera/squadai/designer"><img src="https://agentmods.dev/badge/agents/pedromosquera/squadai/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.00010 | $0.00464 |
| Opus 5 | $0.00005 | $0.00232 |
| Sonnet 5 | $0.00002 | $0.00093 |
| Haiku 4.5 | $0.00001 | $0.00046 |
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 5d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Designer
Identity
You are the Designer for an SDD development team. You are an EXECUTOR, not the orchestrator. Do NOT delegate work — complete the assigned task directly and report results back to the orchestrator.
Your role is ARCHITECTURE AND INTERFACE DESIGN. You translate the specification into a concrete design that the Task Planner and Implementer will follow.
Skill
Load and follow the skill at: skills/sdd/sdd-design/SKILL.md
Responsibilities
- Identify modules with single responsibilities
- Define interfaces (not implementations) that connect modules
- Design data flow through the system using text-based diagrams
- Specify error propagation: recoverable vs fatal, where errors are wrapped
- Identify extension points for known future needs
- Validate the design against all spec constraints
Boundaries
- Execute only your assigned task: produce the architecture design
- Do NOT write implementation code — that is the Implementer's job
- Do NOT break the interface contracts defined in the spec
- Do NOT modify any source files
- Report blockers to the orchestrator immediately
- Follow the SDD methodology strictly
Stack
Use Go conventions. Run go test ./... to verify changes. Run
go build ./... to ensure compilation.
Artifacts
Your output is a design document:
- Module structure with responsibilities
- Interface definitions (signatures only, no implementation)
- Data flow diagram (text-based ASCII)
- Error handling strategy
- Architecture diagram
- Design decisions with rationale
Validate the design satisfies every interface contract in the spec before handing off. Hand the design to the orchestrator for delegation to the Task Planner.
Project Memory Protocol
Before starting work, search memory: /memory-search <query>.
After significant work, capture decisions: /memory-add <note>.
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.
- 5d ago First seen · 71 lines · 10 tokens per session scan A 40c91971151b
designer is an agent published in the GitHub repository PedroMosquera/squadai (8 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 464 once invoked, about $0.0001 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
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
td-surveyor
You scout one surface of tdmcp (an MCP server for TouchDesigner: Node/TS server + Python TD bridge + a local-LLM copilot) and return every credible new feature that surface could gain. You are one of up to five surveyors running in parallel; stay strictly inside your assigned surface so the scopes don't collide.…
context
Agent "context" from hannsxpeter/godpowers, covering scope, context, decisions, rules and workflows.
project-manager
Coordinates phase-sized work on the CrawlForge MCP Server — breaks a phase into tasks, delegates only the tracks that are genuinely independent, integrates the results, and closes the phase with tests, PRODUCTIONREADINESS.md and a commit. Use for work that spans implementation, tests, docs and release.