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 skills/klausfreiberufler/devflow-mcp/devflow-flow-displaynpx skills add KlausFreiberufler/devflow-mcp --skill devflow-flow-displaygit clone --depth 1 https://github.com/KlausFreiberufler/devflow-mcpWrote 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/skills/klausfreiberufler/devflow-mcp/devflow-flow-display)<a href="https://agentmods.dev/skills/klausfreiberufler/devflow-mcp/devflow-flow-display"><img src="https://agentmods.dev/badge/skills/klausfreiberufler/devflow-mcp/devflow-flow-display.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 | $0.00050 | $0.00699 |
| Opus 5 | $0.00025 | $0.00349 |
| Sonnet 5 | $0.00010 | $0.00140 |
| Haiku 4.5 | $0.00005 | $0.00070 |
Grade A, and why
devflow-flow-display 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevFlow — Flow-List Display Convention
When showing flows to the user — in any form — render them as a Markdown table with these columns and rules.
Format
| ID | State | Assignee | Titel |
|---|---|---|---|
| ⭐ **DF-329** | 🔨 in_progress | klaus 🔒 | flow_list MCP-Tool: Browser-Sortierung + … |
| **DF-328** | 💡 idea | — | Knowledge Draft "Accept All" komischer dialog |
Iron Laws
-
⭐ for own flows. If
flow.isMine === true(server-computed: assignee or creator equals the authenticated user), prefix the ID with⭐. No exceptions — this is what makes the user's own work scannable at a glance. -
Lock-status separated from assignee. Active agent sessions get a 🔒 suffix on the assignee column. An idle flow shows just the assignee name (or
—if unassigned). Never write(frei)or other lock-pseudo-text — that conflates two orthogonal concepts. -
Hide done-flows by default. The backlog is about open work. Show only
idea | planning | approval | ready | in_progress | review. Showdoneonly when the user explicitly asks for it ("show all flows", "include done",includeDone: true). -
State icon prefix. Use the canonical icons:
💡 idea·📋 planning·🔒 approval·▶️ ready·🔨 in_progress·🔍 review·✅ done
-
Order matches the browser. The backend already returns flows in the same order as the FlowsPage (kanban_sort_order ASC for project-scope, updated_at DESC for cross-project). Do not re-sort by display_id or alphabetically — preserve the server order.
-
No re-rendering of the MCP-tool output. When
mcp__devflow__flow_listreturns a table, pass it through verbatim. Re-rendering it loses the conventions and risks drift.
When this triggers
- User asks
/devflow-list,flow_list, "show me the flows", "what's open", "what's in the backlog" - User asks for status across flows ("what am I working on", "what's mine")
- You proactively surface flows during planning (e.g. "you also have DF-X open in this area")
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 · 48 lines · 50 tokens per session scan A 040109356744
devflow-flow-display is a skill published in the GitHub repository KlausFreiberufler/devflow-mcp (1 stars, last pushed 5d ago), licensed MIT. It adds 50 tokens to every session and 699 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…