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/geonheeye/multi-agent-dotfiles/subagent-driven-developmentnpx skills add GeonheeYe/multi-agent-dotfiles --skill subagent-driven-developmentgit clone --depth 1 https://github.com/GeonheeYe/multi-agent-dotfilesWhat 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.00017 | $0.02631 |
| Opus 5 | $0.00009 | $0.01316 |
| Sonnet 5 | $0.00003 | $0.00526 |
| Haiku 4.5 | $0.00002 | $0.00263 |
Grade A, and why
subagent-driven-development 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 ships with it
3 files 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.
- 2d ago First seen · 276 lines · 17 tokens per session scan A bb09d067ab62
subagent-driven-development is a skill published in the GitHub repository GeonheeYe/multi-agent-dotfiles (3 stars, last pushed 14d ago), with no licence file. It adds 17 tokens to every session and 2,631 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 skills, from other repositories
audit-history
Use when reviewing past agent sessions, auditing memory health, identifying repeated corrections or friction, cleaning up stale memories, proposing new skills and rules from usage patterns, or identifying mechanical improvements (testing, linting, static analysis, tooling) that could improve outcomes.
create-skill
Use when creating, writing, or authoring a new Cursor agent skill, or when asking about skill structure, SKILL.md format, or skill best practices.
design-agent-loop
Design a reusable agent loop as a graph before running it. Take a TASK and COMPLETION CRITERIA, draw the node graph (input, plan, act, verify, retry or escalate, done), specify context, tools, expected output, and evidence per node, label every transition trigger, set max retries, budget ceilings, and human approval…
define-agent-goal
Turn a rough task into an agent Goal (outcome, verification with 3 to 5 success criteria, constraints, boundaries, iteration policy, stopping condition, and helper goals when parallel work is implied) so an agent can run with minimal babysitting. Plan-only, no execution in the same turn. Use for Goal, delegate, run…
create-rule
Use when creating, writing, or updating a Claude Code rule file (.claude/rules/.md or /.claude/rules/.md), or when asking about rule format, path scoping, or rule best practices.
agent-risk-review
Produces a one-page agent permission brief (allowed, approval-required, forbidden, limits, logging, rollback, first-week test plan) before granting an AI agent access to a system, tool, or account. Use for agent risk review, permission design, MCP/tool access planning, or "what should the agent be allowed to do?".