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/blakeem/ai-prompt-guide-mcp/developgit clone --depth 1 https://github.com/Blakeem/AI-Prompt-Guide-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.00009 | $0.00061 |
| Opus 5 | $0.00005 | $0.00030 |
| Sonnet 5 | $0.00002 | $0.00012 |
| Haiku 4.5 | $0.00001 | $0.00006 |
Grade A, and why
develop 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
Develop
⚠️ REQUIRED WORKFLOW - You MUST follow these instructions:
Load workflow via get_workflow (once per conversation):
get_workflow({ workflow: "develop" })
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 · 13 lines · 9 tokens per session scan A 40ee52632183
develop is a command published in the GitHub repository Blakeem/AI-Prompt-Guide-MCP (4 stars, last pushed 9mo ago), licensed MIT. It adds 9 tokens to every session and 61 once invoked, about $0.0000 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
llmwiki-query
Query a configured llmwiki-serve instance directly from a local project.
tree
Show file tree with sync status indicators showing which files are indexed, modified, new, or deleted.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
pre-mortem
Run a pre-mortem risk analysis on a strategic project before it ships.
maestro-next
Unified entry for all development intents — classify intent, assess complexity, route to the correct execution channel: /maestro-companion (lightweight), standard single run, or /maestro and /maestro-ralph (multi-step manual/orchestrated). Pure router, never runs execution loops itself.
maestro-knowhow
Intent-driven knowhow precipitation — describe what you want to capture (记一个关于X的决策 / 保存这段代码模板 / 写个部署配方 / 存个调试技巧) and the workflow infers the type and records it into .workflow/knowhow/. Pure capture surface; knowhow 的管理/审计走 /maestro-knowledge；项目约束规则走 /maestro-spec add。Triggers on "knowhow capture", "知识沉淀", "沉淀经验"…