tech-spec

tech-spec is a skill for Claude Code, Codex, Cursor from tad-agentics/RAD-Multi-agent. It costs 66 tokens per session (6,215 once invoked), scanned A, original, no licence file.

A set of instructions for producing a technical specification during Phase 4 of a software project. A technical specification describes what the system must do, how it should work, and how its parts connect.

In plain words
What is it for?
Writing specifications that cover functional and non-functional requirements, shared types, data access, APIs, authentication, environment variables, AI use, scheduled jobs, email flows, and checks.
Why use it?
It gives the Phase 4 output a defined structure, so important areas such as requirements, data, authentication, integrations, and quality checks are documented consistently.

Skill for Claude CodeCodexCursor

Install

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.

agentmods
npx agentmods add skills/tad-agentics/rad-multi-agent/tech-spec
Any agent
npx skills add tad-agentics/RAD-Multi-agent --skill tech-spec
Clone the repo
git clone --depth 1 https://github.com/tad-agentics/RAD-Multi-agent

Made for: Claude Code, Codex, Cursor.

Wrote 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.

agentmods badge for tech-spec

README.md
[![agentmods](https://agentmods.dev/badge/skills/tad-agentics/rad-multi-agent/tech-spec.svg)](https://agentmods.dev/skills/tad-agentics/rad-multi-agent/tech-spec)
Your own site
<a href="https://agentmods.dev/skills/tad-agentics/rad-multi-agent/tech-spec"><img src="https://agentmods.dev/badge/skills/tad-agentics/rad-multi-agent/tech-spec.svg" alt="Measured on agentmods" height="20"></a>
Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,215 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00066 $0.06215
Opus 5 $0.00033 $0.03107
Sonnet 5 $0.00013 $0.01243
Haiku 4.5 $0.00007 $0.00622

Measured 3d ago against content hash cba3e5957064, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

tech-spec 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.

.cursor/skills/tech-spec/SKILL.md · 504 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. 3d ago First seen · 504 lines · 66 tokens per session scan A cba3e5957064

Subscribe to this mod's changes

tech-spec is a skill published in the GitHub repository tad-agentics/RAD-Multi-agent (2 stars, last pushed 5mo ago), with no licence file. It adds 66 tokens to every session and 6,215 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens