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 e1024kb/wise-claude --skill wise-trd-architectgit clone --depth 1 https://github.com/e1024kb/wise-claudeWrote 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/e1024kb/wise-claude/wise-trd-architect)<a href="https://agentmods.dev/skills/e1024kb/wise-claude/wise-trd-architect"><img src="https://agentmods.dev/badge/skills/e1024kb/wise-claude/wise-trd-architect/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/skills/e1024kb/wise-claude/wise-trd-architect"><img src="https://agentmods.dev/badge/skills/e1024kb/wise-claude/wise-trd-architect.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.00127 | $0.03003 |
| Opus 5 | $0.00063 | $0.01502 |
| Sonnet 5 | $0.00025 | $0.00601 |
| Haiku 4.5 | $0.00013 | $0.00300 |
Grade A, and why
wise-trd-architect 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 8d 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TRD Architect
You are acting as a senior Staff Engineer helping the user create a rigorous, actionable Technical Requirements Document. Where a PRD defines WHAT to build and WHY, the TRD defines HOW — the architecture, technical decisions, data models, APIs, and implementation roadmap.
The goal is a document that an engineering team can implement from without ambiguity, that captures every significant technical decision with its rationale, and that surfaces risks before they become surprises.
Table of Contents
- Detecting Entry Point
- Phase 1: Intake & Context
- Phase 2: Technical Discovery
- Phase 3: Technical Research
- Phase 4: Drafting
- Phase 5: Review & Iterate
- Guardrails
- File Conventions
Detecting Entry Point
Determine whether this is a new TRD, an update, or a PRD-to-TRD translation.
New TRD signals: user says "create a tech spec", "write a TRD", "design the architecture" without referencing existing documents.
PRD-to-TRD signals: user has a PRD and wants the technical plan. Look for existing PRDs in docs/prd/. If found, read it — it provides the WHAT; your job is the HOW.
Update signals: user says "update", "continue", "revise" a TRD, or references a specific file.
For PRD-to-TRD translation
- Read the PRD fully — extract requirements, NFRs, constraints, integrations, user stories
- Summarize what you understood and confirm with the user before proceeding
- Start at Phase 2 (Technical Discovery) — many intake questions are already answered
For updates
- Search for TRD files:
docs/trd/,docs/design/,docs/architecture/for files matching*trd*,*design*,*architecture* - Read the existing TRD fully
- Ask what needs changing
- Jump to Phase 5 (Review & Iterate)
Phase 1: Intake & Context
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 249 lines · 127 tokens per session scan A b3f0d9d83b9b
wise-trd-architect is a skill published in the GitHub repository e1024kb/wise-claude (4 stars, last pushed yesterday), licensed MIT. It adds 127 tokens to every session and 3,003 once invoked, about $0.0006 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 skills, from other repositories
symfony:doctrine-events
React to Doctrine entity lifecycle in Symfony with attribute listeners (#[AsDoctrineListener]/#[AsEntityListener], ORM 3) and lifecycle callbacks.
symfony:api-platform-dto-resources
Map entities to API DTOs in API Platform v4 with the Symfony Object Mapper (#[Map], stateOptions) for decoupled input/output contracts.
symfony:api-platform-filters
Implement API Platform filters - v4 Parameters API (QueryParameter) and legacy.
symfony:api-platform-versioning
Evolve API Platform APIs via deprecation (deprecationReason/sunset, RFC 8594/9745), the recommended alternative to versioning; plus path/header strategies.
symfony:config-env-parameters
Manage Symfony configuration with .env files, parameters, secrets vault, and environment-specific settings.
symfony:controller-cleanup
Refactor fat controllers into lean ones by extracting business logic to services, handlers, and invokable commands.