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-pattern-reusenpx skills add KlausFreiberufler/devflow-mcp --skill devflow-pattern-reusegit clone --depth 1 https://github.com/KlausFreiberufler/devflow-mcpWhat 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.00060 | $0.01201 |
| Opus 5 | $0.00030 | $0.00600 |
| Sonnet 5 | $0.00012 | $0.00240 |
| Haiku 4.5 | $0.00006 | $0.00120 |
Grade A, and why
devflow-pattern-reuse 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 2d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: devflow-pattern-reuse
Knowledge-Hook 2 implementation. Sister-skill to [[devflow-collision-acknowledged]] (Hook 1) and [[devflow-tdd]] (Hook 3): together they make sure the planning phase is informed by everything the project already knows.
When to use
Use during planning state, after the awareness-list walk (Hook 1) but before submitting the plan to approval. Hook 1 covers the topic-scope (what's in flight, what's deferred). Hook 2 covers the solution-scope (which patterns already address shapes of this problem).
Skip when: the flow has no tags / scope is fully novel / no patterns exist yet in the project (then this becomes a Hook 7 candidate post-done — capture new patterns into the wiki).
Process
1 · Pull existing patterns
Preferred (DF-310): call wiki_get_briefing({flowId}) — returns related ADRs, patterns, runbooks AND the briefing-Markdown automatically scoped to this flow's tags. The agent doesn't have to assemble it manually.
Fallback (manual scope query): for each tag the flow carries, query:
GET /api/projects/:projectId/docs?documentType=pattern&tag=<tag>
Equivalent MCP: doc_page_list({ projectId, document_type: 'pattern', tags: ['<tag>'] }).
Aggregate results across all tags. Deduplicate by page-id.
2 · Triage suggestions
For each pattern: read its problem, solution, when_to_use frontmatter / first paragraph. Classify into:
- strong-match → the pattern's
when_to_usedescribes this exact flow's problem. Use it. - partial-match → applicable to part of the flow. Reference for the relevant section only.
- anti-pattern → the pattern explicitly warns against the path you were considering. Course-correct.
- not-applicable → mention nothing happens, but document
reasonin your plan-decision log so the next person knows you considered + rejected it.
3 · Cite in the plan
For every accepted pattern, write a wiki-link in the relevant plan-section:
## Plan
### Auth flow
We add a JWT-with-refresh-token flow following [[pattern:jwt-auth-with-rotation]] —
this addresses the rotation-on-stale concern without re-deriving the token-rotation logic.
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.
- 2d ago First seen · 112 lines · 60 tokens per session scan A 4062dbc5e208
devflow-pattern-reuse is a skill published in the GitHub repository KlausFreiberufler/devflow-mcp (1 stars, last pushed 4d ago), licensed MIT. It adds 60 tokens to every session and 1,201 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…