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/wjmiracle/projectflow-dag-mcp/projectflow-executenpx skills add wjmiracle/projectflow-dag-mcp --skill projectflow-executegit clone --depth 1 https://github.com/wjmiracle/projectflow-dag-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/wjmiracle/projectflow-dag-mcp/projectflow-execute)<a href="https://agentmods.dev/skills/wjmiracle/projectflow-dag-mcp/projectflow-execute"><img src="https://agentmods.dev/badge/skills/wjmiracle/projectflow-dag-mcp/projectflow-execute.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.1 | $0.00058 | $0.00235 |
| Opus 5 | $0.00029 | $0.00118 |
| Sonnet 5 | $0.00012 | $0.00047 |
| Haiku 4.5 | $0.00006 | $0.00023 |
Grade A, and why
projectflow-execute 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 4d 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
Execute ProjectFlow projects
Use the MCP server as the source of truth. Keep this adapter independent of any particular model.
- Call
projectflow/get_execution_protocolbefore the first execution in a task and follow its returned protocol. - Load the absolute graph path with
load_project, then inspectstatus. - Use
claim_taskfor work. Usenext_taskonly for a read-only preview. - Perform the claimed task in the returned workspace and verify real artifacts.
- Call
done_taskonly with a summary, output paths, and verification evidence. - Use the dedicated fail, block, skip, and reset tools; never bypass MCP by editing the graph JSON.
If the MCP server is unavailable, stop and report the connection problem. Do not silently fall back to unvalidated direct JSON manipulation.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 18 lines · 58 tokens per session scan A befea07cbeb0
projectflow-execute is a skill published in the GitHub repository wjmiracle/projectflow-dag-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 235 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
onboard-repo
Index an unfamiliar codebase into the knowledge graph, then produce a first orientation map -- entry points, most-depended-upon modules, hotspots, test topology.
impact-audit
Blast radius of a change you have not made yet -- traces a symbol across federated repositories, splits impact per repo, and reports what must ship together.
review-pr
Review a PR or branch diff using the knowledge graph for full structural context. Outputs a structured review with blast-radius analysis.
build-graph
Build or update the code review knowledge graph. Run this first to initialize, or let hooks keep it updated automatically.
prompt-optimizer
Analyze raw prompts, identify intent and gaps, match ECC components (skills/commands/agents/hooks), and output a ready-to-paste optimized prompt. Advisory role only — never executes the task itself. TRIGGER when: user says "optimize prompt", "improve my prompt", "how to write a prompt for", "help me prompt", "rewrite…
python-patterns
Pythonic idioms, PEP 8 standards, type hints, and best practices for building robust, efficient, and maintainable Python applications.