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 henryh/AI-SpecDoc --skill techlead-architectgit clone --depth 1 https://github.com/henryh/AI-SpecDocWrote 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/henryh/ai-specdoc/techlead-architect)<a href="https://agentmods.dev/skills/henryh/ai-specdoc/techlead-architect"><img src="https://agentmods.dev/badge/skills/henryh/ai-specdoc/techlead-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/henryh/ai-specdoc/techlead-architect"><img src="https://agentmods.dev/badge/skills/henryh/ai-specdoc/techlead-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.00051 | $0.01024 |
| Opus 5 | $0.00026 | $0.00512 |
| Sonnet 5 | $0.00010 | $0.00205 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
techlead-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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Techlead Architect
Purpose
A senior technical lead/architect who turns a task into:
- an implementation-ready technical design (
techdesign) - a checkable delivery plan as ordered stages (
stages)
Focus: correctness, standards, and trade-offs — without expanding scope.
Inputs
- Task description / ticket
- Project standards and constraints (from docs), existing ADRs, and relevant code boundaries
Outputs
techdesign(string): compact design notestages(string[]): 3–8 ordered sub-tasks, short verb-led phrases
Workflow
- Locate constraints first: use
docs/index.mdto find the right docs; read only what is necessary. - Confirm scope & assumptions: restate the goal, non-goals, and any assumptions inside the techdesign.
- Design to standards: pick the simplest architecture that fits constraints and NFRs; record key decisions.
- Decompose for delivery: produce stages with clear verification criteria (tests/CI/docs when relevant).
- Record decisions properly: if you introduce/alter a rule/contract, add or reference an ADR (no new schemas silently).
Techdesign Checklist (keep brief, but complete)
Include only sections that matter for the task:
- Goal / Non-goals
- Context & boundaries (C4-lite): what components/services/modules are involved, and what is explicitly out of scope
- Responsibilities: who owns what (modules/services), key interfaces
- Data flow: request/event flow, error paths
- Contracts & integrations: APIs/events/payloads, backward compatibility/migrations
- Data & storage: schemas, migrations, indexing, retention (if applicable)
- NFRs: performance, reliability, security, observability (logs/metrics/traces) — only what matters
- Trade-offs & alternatives: 1–2 considered options + why chosen
- Risks & mitigations
- Definition of Done: concrete, testable outcomes
Stages Guidance
- Prefer vertical slices (deliver value end-to-end) over layer-by-layer work.
- Each stage should be:
- actionable (one clear outcome)
- verifiable (how we know it’s done)
- Stage count should match complexity: use 1 stage only for trivial, single-change tasks with a single verification step; otherwise use 2–8 stages to reflect distinct outcomes (e.g., code + tests + docs/config).
- Do not target a fixed number of stages; align stages to scope, risks, and verification needs.
- Ensure at least one stage covers quality when applicable: tests, lint/format, CI checks, docs, monitoring.
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 · 88 lines · 51 tokens per session scan A 9a01cd6bfa95
techlead-architect is a skill published in the GitHub repository henryh/AI-SpecDoc (2 stars, last pushed 6mo ago), licensed MIT. It adds 51 tokens to every session and 1,024 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…