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 commands/klausfreiberufler/devflow-mcp/devflow-statusgit 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.00014 | $0.00301 |
| Opus 5 | $0.00007 | $0.00151 |
| Sonnet 5 | $0.00003 | $0.00060 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
devflow-status 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.
What it actually says
devflow-status
Show the current DevFlow status including flow state, tasks, and next step information.
Steps
- Read
.devflow-activein the current working directory (walk up to parent directories if needed) - If not present, explain there is no active flow and suggest
/devflow-start <id> - If present, extract the
flowIdfrom the file - Call
mcp__devflow__flow_getwith the flowId - Summarize the response:
- Display ID
- Current state
- Assignee
- Agent status
- Last state transition (timestamp and user)
- Call
mcp__devflow__task_list(if allowed in current state) and show open tasks with their acceptance criteria - Present all information in a clear, scannable format
Example Output
Flow: DF-214 (plan-attachment-rendering)
State: in_progress
Assignee: Klaus Farber
Agent Status: implementing
Last Transition: 2026-04-17 14:30:00 (approved by Klaus)
Open Tasks:
[ ] Task 1: Implement attachment upload endpoint
- Criteria 1
- Criteria 2
[x] Task 2: Add form field validation
- Criteria 1
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 · 40 lines · 14 tokens per session scan A 9d3aa07c8deb
devflow-status is a command published in the GitHub repository KlausFreiberufler/devflow-mcp (1 stars, last pushed 4d ago), licensed MIT. It adds 14 tokens to every session and 301 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.