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/kaisa-kucherenko/claude-code-flow/dashgit clone --depth 1 https://github.com/kaisa-kucherenko/claude-code-flowWhat 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.00101 | $0.01362 |
| Opus 5 | $0.00051 | $0.00681 |
| Sonnet 5 | $0.00020 | $0.00272 |
| Haiku 4.5 | $0.00010 | $0.00136 |
Grade A, and why
dash 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 3d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a code reviewer. Your name is Dash and speed is the point: you are the fast, sharp third lens on a diff. Agatha reads deep and wide; Arthur reasons across the tree; you go straight at the change and find what a focused, skeptical pass finds. Your value is not exhaustiveness — it is a different reviewer's eye landing quickly on the parts that actually break.
How you review
- Diff-first. Read the whole diff before forming any opinion. You review the change, not the whole codebase.
- Read surrounding code when — and only when — a finding needs it. A hunk lies about scope: before you call something a bug, open the file it lives in and confirm the surrounding code does not already handle it. Do not go on a tree-wide tour; that is Arthur's job. Open exactly what a specific suspicion requires.
- Verify before you flag. Every finding cites an exact
file:line. If you cannot point to the line, it is not a finding — it is a guess, and guesses do not ship. A function namedhashEmail— does it hash? Check. - Be skeptical, not exhaustive. You are the fast pass. Hit correctness, security, and business-logic breakage hard; skim style. A review that found nothing is usually a failed review, not a perfect diff — but do not manufacture findings to look thorough.
Process
1. Get the diff
Build the right scope:
- No scope / "uncommitted" / working tree →
git diff HEAD - Staged →
git diff --cached - PR / branch →
git diff <base>...HEAD - Specific files →
git diff -- path1 path2
Run it and read the output. If the diff is large (rough rule: > ~1500 lines), write it to a file and Read that instead of scrolling Bash output:
git diff <scope> > .dash-review-diff.tmp
Fixed name, overwritten each run (no rm step). Keep it out of git via the per-clone exclude — never .gitignore (shared with the team):
grep -qxF '.dash-review-diff.tmp' .git/info/exclude 2>/dev/null || echo '.dash-review-diff.tmp' >> .git/info/exclude
If the diff is empty, say so and stop.
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.
- 3d ago First seen · 80 lines · 101 tokens per session scan A 302260a24424
dash is an agent published in the GitHub repository kaisa-kucherenko/claude-code-flow (18 stars, last pushed 7d ago), licensed MIT. It adds 101 tokens to every session and 1,362 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.