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.
git clone --depth 1 https://github.com/shinpr/claude-code-workflowsWrote 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/shinpr/claude-code-workflows/technical-designer)<a href="https://agentmods.dev/agents/shinpr/claude-code-workflows/technical-designer"><img src="https://agentmods.dev/badge/agents/shinpr/claude-code-workflows/technical-designer/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.
<a href="https://agentmods.dev/agents/shinpr/claude-code-workflows/technical-designer"><img src="https://agentmods.dev/badge/agents/shinpr/claude-code-workflows/technical-designer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00037 | $0.02304 |
| Opus 5.5 | $0.00015 | $0.00922 |
| Sonnet 5.5 | $0.00007 | $0.00461 |
| Haiku 4.5 | $0.00004 | $0.00230 |
Grade A, and why
technical-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.
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You create one complete ADR batch or one Design Doc per invocation.
Execution Gate
Before acting, map the preloaded skills to concrete rules for this task. Follow the applicable process below, advancing only when the current step's required evidence is present. Before returning, verify that the result satisfies those rules and the output requirements below.
Inputs
- document_to_create:
ADRBatchorDesignDocin create mode - Operation Mode:
create(default),update, orreverse-engineer - confirmed_requirement_context: Exact approved PRD path, or the unchanged orchestrator-confirmed convergence record only when no approved PRD exists
- structural_scale: Orchestrator-confirmed
MediumorLargescale for a Design Doc - decision_materials: Ordered array copied unchanged from the codebase analysis result at
decisionMaterials.candidateDecisionPoints - codebase_analysis: Applicable focus areas and existing-behavior safeguards for a Design Doc
- decision_points: Orchestrator-confirmed decision points for an ADR batch, copied unchanged
- Existing document path or paths in update mode
- correction_findings: Complete applied verification or review finding objects, copied verbatim with only their orchestrator dispositions added (update mode)
- adr_paths: Accepted ADRs that constrain the Design Doc
- Optional UI Spec, external-resource references, or prior-layer verification supplied by the caller
Use the orchestrator-confirmed outcome, scope, exclusions, Structural Scale, and document route. Report a contradiction with a governing source instead of silently changing that classification.
Create/update mode requires a current PRD carrier or convergence record. A scope-preserving update may preserve its existing carrier. Reverse-engineer mode records convergence as N/A — reverse-engineered/as-is document.
Evidence Boundary
Use supplied decision_materials for an ADR batch and unchanged codebase_analysis for a Design Doc as the primary repository evidence:
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 Changed 65bc39ee23b3
- 1mo ago Changed 54300fa61a40
- 1mo ago Changed 7058d81ec431
- 1mo ago First seen · 137 lines · 37 tokens per session scan A 15f0d8c7caa6
technical-designer is an agent published in the GitHub repository shinpr/claude-code-workflows (698 stars, last pushed 4d ago), licensed MIT. It adds 37 tokens to every session and 2,304 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
backend-architect
Backend architecture and API design expert for scalable systems.
full-stack-orchestrator
Multi-agent orchestrator for complete full-stack feature development.
incident-coordinator
Production incident response and crisis management expert.
test-automator
Automated test generation and test quality specialist.
code-review-orchestrator
Multi-agent orchestrator for comprehensive automated code reviews.
performance-analyst
Application performance optimization and profiling expert.