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/a1f/agent-templates/to-ddnpx skills add a1f/agent-templates --skill to-ddgit clone --depth 1 https://github.com/a1f/agent-templatesWrote 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/a1f/agent-templates/to-dd)<a href="https://agentmods.dev/skills/a1f/agent-templates/to-dd"><img src="https://agentmods.dev/badge/skills/a1f/agent-templates/to-dd.svg" alt="Measured on agentmods" 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.00032 | $0.01417 |
| Opus 5 | $0.00016 | $0.00709 |
| Sonnet 5 | $0.00006 | $0.00283 |
| Haiku 4.5 | $0.00003 | $0.00142 |
Grade A, and why
to-dd 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 5d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
To DD
Turn the conversation and codebase into a short design document a human actually
reads, published as a claude.ai artifact. That artifact is the plan's single
source of truth: /to-slices writes the implementation plan into it and /to-tasks
writes the task map into it later. This skill creates no GitHub issue — the
tracker appears only when execution starts (/to-tasks opens it).
/to-dd [--title="..."] [--url=<artifact url>]
1. Gather context (conversation + light repo read)
2. Clarify gaps via AskUserQuestion (gate, only if thin)
3. Draft the doc
4. Show it, wait for approval (gate)
5. Publish the artifact; print the URL
Arguments
| Arg | Default | Notes |
|---|---|---|
--title="..." |
Derived from context | The doc's title — what we're building |
--url=... |
Publish new | Re-publish: update that artifact in place, keeping any Implementation plan / Tasks content already on it |
Phase 1 — Gather context
Read the conversation; explore the repo only if you haven't. Use the codebase's own vocabulary and respect existing ADRs.
Phase 2 — Clarify (gate)
If a fact that changes the design is missing, ask with AskUserQuestion (≤4 at a time) — otherwise skip when context is rich. Every question offers concrete options, and the recommended option's description states why it wins — the trade-off that drives the pick. A bare "(Recommended)" with no reason is not an option.
Phase 3 — Draft
Write it tight — a beautiful blog post, not a spec:
- Very short. Cut anything that doesn't change a decision or teach the reader.
- Plain English, no filler. Ban "robust", "seamless", "leverage", "comprehensive", "powerful" — and all hedging. Short declarative sentences. Concrete nouns.
- Full sentences, never fragment bullets. A list of three-word bullets that could caption anything ("improve UX", "add validation") is slop — if a point is worth listing, it is worth one real sentence that a reader can act on.
- Only what was discussed or confirmed — invent nothing.
- High level: name modules and capabilities, not file paths or code; they rot. Rare exception: a tiny snippet that nails a decision — a type, a schema.
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.
- 5d ago First seen · 121 lines · 32 tokens per session scan A 7f84ef8f3a31
to-dd is a skill published in the GitHub repository a1f/agent-templates (2 stars, last pushed 5d ago), licensed MIT. It adds 32 tokens to every session and 1,417 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-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…