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 agentmods add skills/leifericf/agentic-sdk/design-technicalnpx skills add leifericf/agentic-sdk --skill design-technicalgit clone --depth 1 https://github.com/leifericf/agentic-sdkWhat 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 | $0.00012 | $0.00476 |
| Opus 5 | $0.00006 | $0.00238 |
| Sonnet 5 | $0.00002 | $0.00095 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
design-technical 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.
What it actually says
design-technical
Design a simple, evolvable system with clear boundaries and data flows. Prefer operational simplicity; make tradeoffs explicit and recorded. Express the design in Functional Core / Imperative Shell terms for the project's active languages (C, Zig, Clojure, Elixir).
Procedure
- Read
project-meta.md,problem-description.md,product-requirements.md,risk-assumption-review.md,decision-log.md, andopen-questions.md. Theux-design-guide.mdis optional; proceed without it when the UX step was skipped. If a required prerequisite is missing, returnblocked: <which artifact>. - Surface and resolve
[Blocking]items affectingtechnical-design.md. - Ask the smallest set of clarifications, at most three per turn: system boundaries and key flows, data durability and retention, external integrations and their failure behavior, operational posture, team constraints, and repo conventions.
- Set project-wide defaults (not per-feature): observability (logging, metrics, tracing) and testing posture (unit, integration, e2e). Starting points, refined per feature.
- Record decisions in
decision-log.mdwith date, decision, rationale, tradeoff. - Write
~/.agentic-sdk/<project>/artifacts/planning/technical-design.mdwith: Metadata, System Shape, Domain Boundaries, Components, Key Flows, Data Model, Integrity Strategy, Audit and Compliance, Integrations, Technology Stack (backend, frontend if applicable, data, infrastructure, observability, testing), Repository and Delivery Conventions (structure, command surface, CI outline, environment model), Evolution Strategy, Known Tradeoffs. Split components and modules along the FC/IS line.
Boundaries
Owns system architecture, components, data flows, and the stack. create-backlog owns the work breakdown; design-ux owns the interface. Reached by plan-system.
Return
One line: the artifact written and a terse status, or blocked: <reason>.
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 First seen · 48 lines · 12 tokens per session scan A 016bf56e10e7
design-technical is a skill published in the GitHub repository leifericf/agentic-sdk (5 stars, last pushed 14d ago), licensed MIT. It adds 12 tokens to every session and 476 once invoked, about $0.0001 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.
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.
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.
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.
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.
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…