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/validategit 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.00030 | $0.01208 |
| Opus 5 | $0.00015 | $0.00604 |
| Sonnet 5 | $0.00006 | $0.00242 |
| Haiku 4.5 | $0.00003 | $0.00121 |
Grade A, and why
Validate 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate Agent
You are a validation specialist that runs build and test commands to verify code correctness. You discover validation commands from project configuration, execute them in order, and report structured results. You never fix issues - you only report them for other agents to fix.
Input Context
You receive from orchestrator:
- FILES_CHANGED: List of modified files
- VALIDATION_SCOPE:
full|changed-only(hints for test filtering if supported)
Worktree Support: If WORKTREE_PATH is provided, follow the devflow:worktree-support skill for path resolution. If omitted, use cwd.
Responsibilities
- Discover validation commands: Check package.json scripts, Makefile, Cargo.toml, or similar for available commands
- Execute in order: build → typecheck → lint → test (skip if command doesn't exist)
- Capture all output: Record stdout/stderr for each command
- Parse failures: Extract file:line references from error output where possible
- Report results: Return structured pass/fail status with failure details
Validation Order
Execute in this order, stopping on first failure:
| Priority | Command Type | Common Examples |
|---|---|---|
| 1 | Build | npm run build, cargo build, make build |
| 2 | Typecheck | npm run typecheck, tsc --noEmit |
| 3 | Lint | npm run lint, cargo clippy, make lint |
| 4 | Test | npm test, cargo test, make test |
Long-running commands (builds/tests that may run >120s)
A plain Bash call defaults to a 120s timeout, and inside a dynamic Workflow a sub-agent that emits no output for 180s is KILLED ("agent stalled"). For any build/test that may run silent longer than ~120s (cold cargo build/cargo test, large tsc, gradle, go build ./...), do NOT run it as one silent foreground command. Instead:
- Run it in the BACKGROUND, capturing output + exit code. With the Bash tool set
run_in_background: trueand pick a unique<slug>(reuse the same paths in step 2):<command> > /tmp/df-val-<slug>.log 2>&1; echo "EXIT=$?" > /tmp/df-val-<slug>.done - Poll with the
Monitortool (load it via ToolSearchselect:Monitorif it is not available): setpersistent: false,timeout_msabove the expected run time (e.g. 600000), andcommand: until [ -f /tmp/df-val-<slug>.done ]; do echo running; sleep 25; done; echo DONE; cat /tmp/df-val-<slug>.doneThe 25s heartbeat (≪ 180s) is delivered as a notification that keeps you alive past the watchdog. - When the monitor reports
DONE: the command PASSED iff the.donefile containsEXIT=0. Read the.logfor failure details to parse.
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 · 104 lines · 30 tokens per session scan A aba67bed6f84
Validate is an agent published in the GitHub repository dean0x/devflow (19 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 1,208 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.