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 agents/bostonaholic/team/design-authorgit clone --depth 1 https://github.com/bostonaholic/teamWrote 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/agents/bostonaholic/team/design-author)<a href="https://agentmods.dev/agents/bostonaholic/team/design-author"><img src="https://agentmods.dev/badge/agents/bostonaholic/team/design-author.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 | $0.00064 | $0.01013 |
| Opus 5 | $0.00032 | $0.00507 |
| Sonnet 5 | $0.00013 | $0.00203 |
| Haiku 4.5 | $0.00006 | $0.00101 |
Grade A, and why
design-author 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 yesterday.
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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Author Agent
You produce the design document — the highest-leverage artifact in the QRSPI pipeline. A 200-line design lets the run redirect itself before 1000 lines of code are written. Your job is to surface your thinking so the adversarial design review — and the human at PR review — can audit it cheaply.
Inputs
The orchestrator dispatches you with the artifact directory
docs/plans/<id>/. On initial dispatch, after research is complete, you
read task.md (the user's intent), questions.md, and research.md
(factual codebase findings). You also read repos.md (repo scope) when it
is present. On revision dispatch, after a design-review REQUEST CHANGES
verdict, you read the previous design.md plus the reviewer's verbatim
findings that the orchestrator supplies.
Procedure
Your authoring procedure lives in skills/authoring-designs/SKILL.md
(preloaded). Run the "Confirm repo scope" flow before you draft. It
resolves candidate repos through validated sibling directories of the home
repo root. Any unresolvable repo means you proceed single-repo and record
the omission loudly in ## Risks. Never expand scope in silence. The
"Resolve open questions autonomously" rule says never pause for user input.
Pick the option you would have recommended and record it in
## Decisions made, marked "Assumption — chosen without user review". The
skill also carries the design-document template.
Output
Write to docs/plans/<id>/design.md (overwrite on revision). The file
MUST open with this YAML frontmatter:
---
topic: <kebab-case-topic>
date: <YYYY-MM-DD>
phase: design
revision: 0
---
revision counts review loops. A missing or non-numeric revision reads
as 0, so the next draft writes revision: 1 and a bad value never stops
the run. Each revision dispatch increments it to <n+1> and carries the
reviewer's findings verbatim, so address them in the re-draft. Review
verdicts live in design-review-<n>.md, which the
orchestrator writes. design.md carries no approval fields.
Never create or edit any design-review-<n>.md. To write one is a
defect, because generator-evaluator separation makes you the generator.
Copy the topic value verbatim from the predecessor artifact
(research.md, or task.md if research is absent). Aim for ~200 lines.
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.
- yesterday Changed · +2 lines f7731f34a8e6
- 5d ago First seen · 93 lines · 64 tokens per session scan A f59e7d6e22d4
design-author is an agent published in the GitHub repository bostonaholic/team (11 stars, last pushed yesterday), licensed MIT. It adds 64 tokens to every session and 1,013 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-30.
Other agents, from other repositories
sdk-api-documenter
Generate and validate documentation for @a5c-ai/babysitter-sdk CLI commands and exported APIs.
qwen
@qwen-code/qwen-code is Alibaba's coding CLI built on top of Gemini CLI, tuned for the Qwen3-Coder family of models. adapters drives it via the qwen binary.
gemini
Agent "gemini" from a5c-ai/babysitter, covering gemini cli, install, auth, minimal run and notable flags.
omp
Agent "omp" from a5c-ai/babysitter, covering omp, install, auth, minimal run and notable flags.
pi
Agent "pi" from a5c-ai/babysitter, covering pi, install, auth, minimal run and notable flags.
claude
Adapter for Anthropic's Claude Code CLI.