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 skills add darellchua2/opencode-config-template --skill technical-design-creation-skillgit clone --depth 1 https://github.com/darellchua2/opencode-config-templateWrote 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/skills/darellchua2/opencode-config-template/technical-design-creation-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/technical-design-creation-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/technical-design-creation-skill.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00045 | $0.03046 |
| Opus 5 | $0.00023 | $0.01523 |
| Sonnet 5 | $0.00009 | $0.00609 |
| Haiku 4.5 | $0.00005 | $0.00305 |
Grade A, and why
technical-design-creation-skill 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.
How it starts
The opening of the file, as written. The whole thing — 377 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
I provide a structured Technical Design Document (TDD) creation template — the engineering "how" stage of the document ladder, filling the gap between the SRS (requirements) and implementation.
- TDD Template — 7-part structure (System Context / Architecture / Data Model / API Surface / Architecture Decision Records / Sequence Diagrams / Non-Functional Design)
- docs/technical-design/ Naming Convention — ticket-linked files (
TDD-{key}.md) - Architecture Decision Records (ADRs) — durable record of WHY each architecture decision was made
- CodeGraph-grounded design — architecture must be validated against the actual codebase, not assumptions
Position in the document ladder: Vision (customer-facing) → BRD (sponsor/stakeholder) → SRS (internal functional/technical requirements) → TDD (this template: engineering design) → implementation. The TDD translates the SRS's functional requirements into architecture, data model, and API contracts.
Name note: "TDD" here means Technical Design Document — NOT Test Driven Development. To avoid collision, the authoring subagent is named
technical-design-specialist-subagent(nottdd-specialist), distinct from the existingtdd-subagent(Test Driven Development) andtdd-workflow-skill.
When to use me
Use this skill when:
- An SRS or feature spec needs to be translated into a concrete engineering design
- Someone says "technical design", "architecture document", "system design", "design spec", "create technical design"
- Architecture decisions need to be captured as durable ADRs (context → decision → consequences)
- The team needs a shared blueprint before implementation begins
Do NOT use for: requirements (use srs-creation-skill/brd-creation-skill); customer-facing vision (use vision-creation-skill); running tests (use tdd-workflow-skill — different TDD).
Trigger phrases: "technical design", "architecture document", "system design", "technical design doc", "design spec", "create technical design", "design the architecture"
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.
- 4d ago First seen · 377 lines · 45 tokens per session scan A 66accb684a88
technical-design-creation-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 45 tokens to every session and 3,046 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-03.
Other skills, from other repositories
horse-database-pooling
Guide for setting up thread-safe database connection pooling (FireDAC / UniDAC) in multithreaded Horse applications.
horse-mvc-architecture
Guide for structuring corporate Horse applications using Clean MVC (Model-View-Controller) principles and decoupling HTTP layers from business logic.
horse-request-response
Guide to interacting with THorseRequest (body, query, params, headers) and THorseResponse (Send, Status, ContentType).
horse-dependency-injection
Guide for managing request-scoped contextual services and IoC (dependency injection) in Delphi and Lazarus.
horse-lazarus-compatibility
Guide for ensuring Lazarus and Free Pascal (FPC) compatibility, addressing anonymous methods differences, JSON units, and compiler directives.
horse-performance-tuning
Guide for optimizing performance, tuning memory alocations, handling large payloads, and adjusting provider execution pipelines.