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 freezingfunky/ashwin-skills --skill agent-designgit clone --depth 1 https://github.com/freezingfunky/ashwin-skillsWrote 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/freezingfunky/ashwin-skills/agent-design)<a href="https://agentmods.dev/skills/freezingfunky/ashwin-skills/agent-design"><img src="https://agentmods.dev/badge/skills/freezingfunky/ashwin-skills/agent-design.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.00094 | $0.01964 |
| Opus 5 | $0.00047 | $0.00982 |
| Sonnet 5 | $0.00019 | $0.00393 |
| Haiku 4.5 | $0.00009 | $0.00196 |
Grade A, and why
agent-design 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent design — decision map, then four pillars
Most "I'm not good at building agents" is really "I build them by feel and can't predict whether the next one will be good." The fix is to name the method.
A working agent is four things, and a weak agent is usually missing one:
Task · Context · Memory · Eval.
But first: one agent = one outcome. If you can name two outcomes that succeed or fail independently, you have two agents — each gets its own design pass.
0. Decision map — singular outcome or split
Do this before filling the pillars. Completion criterion: either (a) one singular DONE/FAILED pair locked, or (b) an explicit split list, this session designs one, and parked agents are either fan-out-spawned after confirm or left for later re-entry.
Steps
- Draft the singular outcome in one sentence (what "this agent worked" means).
- List aspects that feel like separate focuses (intake, summarize, notify, …).
- Smell test each aspect: same DONE/FAILED as the draft outcome?
- Same → keep inside this agent.
- Independent success/fail → split into a separate agent name + its DONE.
- Emit one of:
- One agent — proceed to pillars below for that outcome.
- Multiple agents — print the full split table (name · DONE · FAILED). Pick one to design in this session (recommend the dependency-root). Park the rest. Then run §0b Fan-out before or while continuing pillars for the in-session agent.
- Fog vs size:
- One outcome, still foggy (open decisions) → stay in the decision map; resolve open questions one at a time until the outcome is sharp.
- One outcome, too big for one run → still one agent design; use handoff/memory across runs — do not invent a second agent unless the outcome splits.
0b. Fan-out (parked agents → parallel sessions)
Never spawn without an explicit user confirm. Silent fan-out is a failure mode.
After the split list is on screen, ask once:
What ships with it
1 file 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 · 175 lines · 94 tokens per session scan A 45a9e82be40e
agent-design is a skill published in the GitHub repository freezingfunky/ashwin-skills (2 stars, last pushed 21d ago), licensed MIT. It adds 94 tokens to every session and 1,964 once invoked, about $0.0005 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
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
requirements-authoring
To author, update, and validate functional/non-functional requirements as atomic units with user approval.
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
ijfw-workflow
Use when the user says: 'build', 'create', 'plan', 'new project', 'brainstorm', 'design', 'UI', 'website', 'dashboard', 'app', 'help me build', 'launch', 'book', 'campaign', or anything project-level. Skill body decides Quick vs Deep path.
ijfw-plan
Use when the user says 'plan this', 'plan it', 'make a plan', 'let's plan', 'draft a plan', 'how should we tackle this', 'break this down', or invokes '/ijfw-plan'. Produces a falsifiable PLAN.md (software, book, campaign, design, research) with task breakdown, dependency wave-table, and success criteria — gated by…
ijfw-writing-skills
Authoring discipline for new IJFW skills. Use when creating a new skill, writing a skill, making a skill that does X, or asked to add a skill. Trigger: create a new skill, write a skill, new skill, make me a skill, skill that does, /ijfw-writing-skills.