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/mtrdesign/whygraph/whygraph-plannpx skills add mtrdesign/whygraph --skill whygraph-plangit clone --depth 1 https://github.com/mtrdesign/whygraphWhat 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.00054 | $0.01232 |
| Opus 5 | $0.00027 | $0.00616 |
| Sonnet 5 | $0.00011 | $0.00246 |
| Haiku 4.5 | $0.00005 | $0.00123 |
Grade A, and why
whygraph-plan 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 91 lines · 54 tokens per session scan A 8c9a67251ddf
whygraph-plan is a skill published in the GitHub repository mtrdesign/whygraph (4 stars, last pushed 25d ago), with no licence file. It adds 54 tokens to every session and 1,232 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
claude-plan
Get an independent architecture/implementation plan from Anthropic Claude (Fable, a different vendor's model) running Claude Code's native plan mode, from inside a non-Claude host such as Codex. Use mid-execution when work hits a genuine design fork or high-stakes decision that should not be settled unilaterally. Not…
creating-workflows
当用户想「创建/生成一个 workflow(可复用的多子-agent 编排脚本)」时使用。讲清 deepx workflow 的 JavaScript 脚本格式、可用 API,以及如何用 Workflow 工具保存与运行。.
subagent-driven-development
Execute plan by dispatching fresh subagent per task, with two-stage review after each: spec compliance review first, then code quality review.
repo-harness
Route explicit repo-harness setup, planning, execution, verification, and handoff actions through deterministic repository state.
openspec
规格驱动开发(SDD)。实现任何功能或改动时使用——写代码前先就规格达成一致:在 openspec/changes/ / 写 proposal、spec deltas、tasks(复杂时加 design),对齐后再严格按规格实现,完成后把 delta 归档进基线 specs/。.
karpathy-guidelines
减少 LLM 常见编码错误的行为准则。在写代码、审查或重构时使用:避免过度复杂、做最小化精准改动、显式暴露假设、定义可验证的成功标准。.