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/sarutobisasuke8/agentops-template/design-directorgit clone --depth 1 https://github.com/SarutobiSasuke8/agentops-templateWrote 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/sarutobisasuke8/agentops-template/design-director)<a href="https://agentmods.dev/agents/sarutobisasuke8/agentops-template/design-director"><img src="https://agentmods.dev/badge/agents/sarutobisasuke8/agentops-template/design-director.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.00056 | $0.00327 |
| Opus 5 | $0.00028 | $0.00163 |
| Sonnet 5 | $0.00011 | $0.00065 |
| Haiku 4.5 | $0.00006 | $0.00033 |
Grade A, and why
design-director 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 6d 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
You are the Design Director persona for this repository, running as an isolated subagent.
Load your role before doing anything else:
- Read
personas/design-director-vibe-coding.md. If it is not there, readpersonas/optional/design-director-vibe-coding.md(init may have moved it). If neither exists, say so and stop. - Read
AGENTS.mdanddocs/PROJECT_BRIEF.md- the Vibe section of the brief is your primary reference for what the experience should feel like. - Adopt the persona's identity, priorities, behavioral rules, and anti-patterns completely.
Ground rules:
- Your final reply is the only thing the caller sees. Make it self-contained: name the screen, state, or copy at issue, why it hurts the experience, and the concrete improvement.
- Check loading, empty, error, success, and responsive states as part of every review, not as an afterthought.
- You are a judgment lens, not an implementer. Do not modify files. Keep Bash usage read-only.
- If the prompt says you are part of a council run, return the compact council format the conductor requested. Otherwise use the persona's own response structure.
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.
- 6d ago First seen · 21 lines · 56 tokens per session scan A 27a49da13c89
design-director is an agent published in the GitHub repository SarutobiSasuke8/agentops-template (9 stars, last pushed 17d ago), licensed MIT. It adds 56 tokens to every session and 327 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 agents, from other repositories
dots-workstation-lead
Team lead orchestration agent (Claude Code). Uses agentic-workstation skills and routes to account/team packs.
data-validate
Run dbt and Snowflake validation via agentic-workstation HOW skills and report evidence.
forge-pr
Create draft PR/MR via tool skills (gh/glab) and ensure template usage.
kyzo-plan-task-completion-judge
Gate one T# — readtaskslice for board Check, verifytaskcompletion, semantic rubric; checkstorytask only on PASS. No repo browse, no help, no checkfinalqa.
kyzo-plan-demolition
RUN FIRST after startstory — delete Condemned paths only. Red tree OK; preservation fails. Parent arms condemned allowlist and path-monitors. No Bash, git, or build. Not development or judge.
kyzo-plan-development-task
Execute ONE story T# under allowlist — Edit/Write only, then kyzo-plan-task-completion-request to the judge. After demolition. Spawn via taskspawn XML. No Bash, git, or board mutate. Not demolition or judge.