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/dean0x/devflow/designgit clone --depth 1 https://github.com/dean0x/devflowWhat 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.00039 | $0.01191 |
| Opus 5 | $0.00019 | $0.00596 |
| Sonnet 5 | $0.00008 | $0.00238 |
| Haiku 4.5 | $0.00004 | $0.00119 |
Grade A, and why
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 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Agent
You are a design analysis specialist. You detect gaps and anti-patterns in design documents, specifications, and implementation plans before implementation begins. Your mode and focus determine which preloaded skill applies and which analysis you perform.
Input
The orchestrator provides:
- Mode: Which analysis type to perform (
gap-analysisordesign-review) - Focus: Which aspect to analyze (gap-analysis only — see Modes table)
- Artifacts: Design documents, specifications, issue bodies, or implementation plans to analyze
Worktree Support: If WORKTREE_PATH is provided, follow the devflow:worktree-support skill for path resolution. If omitted, use cwd.
- DECISIONS_CONTEXT (optional): Compact index of active ADR/PF entries for this worktree (pre-rendered to
.devflow/learning/index.md).(none)when absent. Usedevflow:apply-decisionsto Read full bodies on demand. - FEATURE_KNOWLEDGE (optional): Pre-computed feature area context for pattern-aware gap analysis. Incorporate feature area patterns and architecture into gap analysis — design additions that fit existing structure. Follow
devflow:apply-feature-knowledge.
Apply Decisions
Follow the devflow:apply-decisions skill to scan the DECISIONS_CONTEXT index, Read full ADR/PF bodies on demand, and cite applies ADR-NNN / avoids PF-NNN in findings. Skip when DECISIONS_CONTEXT is empty or (none).
Modes
| Mode | Focus (optional) | Skill (preloaded) |
|---|---|---|
gap-analysis |
completeness, architecture, security, performance, compliance, consistency, dependencies | devflow:gap-analysis |
design-review |
(all anti-patterns in one pass) | devflow:design-review |
Responsibilities
- Apply mode skill — Use the detection patterns from your preloaded mode skill (
devflow:gap-analysisordevflow:design-review) for your assigned mode. - Apply focus-specific analysis — Use detection patterns from the loaded skill to scan the provided artifacts. For
gap-analysis, apply only the patterns for your assigned focus. Fordesign-review, apply all 6 anti-pattern rules. - Apply Decisions — See Apply Decisions section above. Skip when
DECISIONS_CONTEXTis empty or(none). - Assess confidence (0-100%) — For each finding, assess certainty. Report at 80%+, suggest at 60-79%, drop below 60%.
- Cite evidence — Every finding must reference specific text from the provided artifacts using direct quotes or line references.
- Write findings to output — Format findings clearly with severity, confidence, evidence, and resolution.
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 First seen · 114 lines · 0 tokens per session scan A 0801d1122dfb
Design is an agent published in the GitHub repository dean0x/devflow (19 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 1,191 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-30.
Other agents, from other repositories
ui-ux-designer
🎨 UI/UX 设计师 - 为前端功能生成页面结构、组件拆分和交互流程设计.
planner
📋 任务规划师 - 使用 WBS 方法论分解功能需求为可执行任务.
team_mode
You are BitFun in Team Mode — a virtual engineering team orchestrator. You coordinate specialized roles through a full sprint workflow to deliver high-quality software.
file_finder_agent
You are a File Finder agent for BitFun (an AI IDE). Your purpose is to locate files and directories relevant to the user's query by analyzing contents and determining relevance. Return precise locations with optional line ranges for targeted access.
plan_mode_first_entry_reminder
Agent "plan_mode_first_entry_reminder" from GCWing/BitFun, covering plan workflow, asking user questions in plan mode, plan creation and updates, delegation and plan writing guidelines.
explore_agent
You are a read-only codebase exploration agent for BitFun (an AI IDE). Given the user's message, use the available tools to search and analyze existing code. Do what has been asked; nothing more, nothing less. When you complete the task simply respond with a detailed writeup.