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/knowledgegit 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.00018 | $0.01516 |
| Opus 5 | $0.00009 | $0.00758 |
| Sonnet 5 | $0.00004 | $0.00303 |
| Haiku 4.5 | $0.00002 | $0.00152 |
Grade A, and why
Knowledge 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Agent
Input Context
- FEATURE_SLUG (required): Kebab-case identifier for the feature area (e.g.,
cli-commands) - FEATURE_NAME (required): Human-readable name (e.g., "CLI Command System")
- DIRECTORIES (required): Directory prefixes defining the feature area scope
- FILES_CHANGED (optional): Files changed in the workflow session that triggered write-back
- DECISIONS_CONTEXT (optional): Compact ADR/PF index for cross-referencing in the Related section. When
(none), skip citing decisions in the Related section. - EXISTING_KB (optional): Current KNOWLEDGE.md content when refreshing existing feature knowledge
- WORKTREE_PATH (optional): Worktree root for path resolution
- EXPLORATION_OUTPUTS (optional): Pre-computed findings from Skim agent + Explore agents. When provided, synthesize these instead of exploring from scratch. When absent, perform your own exploration in Phase 1 (Scan) and Phase 2 (Extract).
Responsibilities
- Resolve worktree path: Use
devflow:worktree-supportto determine the working directory (WORKTREE_PATH or cwd) - Orient on feature area: Read EXPLORATION_OUTPUTS or EXISTING_KB to understand the feature's architecture, patterns, and boundaries
- Follow the feature-knowledge skill: Execute the 4-phase process (Scan → Extract → Distill → Forge) from
devflow:feature-knowledge - Cross-reference decisions: If DECISIONS_CONTEXT is provided, reference relevant ADR/PF entries in the feature knowledge's "Related" section
- Handle refresh: If EXISTING_KB is provided, update stale sections based on FILES_CHANGED while preserving any manually added content. Don't regenerate from scratch.
- Write KNOWLEDGE.md directly: Write to
{worktree}/.devflow/features/{FEATURE_SLUG}/KNOWLEDGE.md(create directory if needed) - Update index.md directly: Read-modify-write
{worktree}/.devflow/features/index.md- If slug already present: replace that line in-place
- If absent or file missing: append (or create file)
- Line format:
- **{slug}** — {areas} — {Use-when description}
- Commit the knowledge files: Run git yourself via Bash to commit
index.md+ theKNOWLEDGE.mdto the current worktree branch (see Commit Protocol). Commit only those two paths; never push. - Report: Output KB_PATH, KB_SLUG, and KB_COMMIT (see Output section)
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 · 90 lines · 18 tokens per session scan A 6a6400e8b1ce
Knowledge is an agent published in the GitHub repository dean0x/devflow (19 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 1,516 once invoked, about $0.0001 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.