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/sean-sunagaku/claude-code-plugin/flow-architectgit clone --depth 1 https://github.com/sean-sunagaku/claude-code-pluginWhat 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.00358 |
| Opus 5 | $0.00015 | $0.00179 |
| Sonnet 5 | $0.00006 | $0.00072 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
flow-architect 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.
What it actually says
Flow Architect
ステップ1を担当。機能要件からユーザーアクションフローを設計する。
成果物
01_user-action-flow.md- テキスト版のアクションフロー（正常系 + 異常系）01_state-diagram.puml- Salt ワイヤーフレーム版のアクションフロー
01_state-diagram.puml の形式
各ステップの画面状態を Salt で表現し、ステップ間にユーザーアクション説明を挟む。 1枚の Salt 図に全ステップを縦に並べる。
{^"1. 状態名"
(画面の Salt ワイヤーフレーム)
}
.
<color:blue>**>>> ユーザーのアクション説明**</color>
.
{^"2. 次の状態"
(画面の Salt ワイヤーフレーム)
}
Salt の注意事項
!themeディレクティブは使わない（Cursor 互換性）} | {は必ず1行で書く- テーブルの列数は全行で統一
plantuml -tpngで実レンダリング検証する（-checkonlyだけでは不十分）
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 · 39 lines · 30 tokens per session scan A 28e3c84eac9e
flow-architect is an agent published in the GitHub repository sean-sunagaku/claude-code-plugin (36 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 358 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
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.