team-planner

A command for setting up the information needed to create a DMAP plugin, including the plugin installation path.

In plain words
What is it for?
Use it before planning a DMAP plugin when you need to record the plugin’s absolute path in AGENTS.md.
Why use it?
It makes the plugin location explicit so later commands can find the required files and follow the correct setup.

Command

Install

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.

agentmods
npx agentmods add commands/unicorn-plugins/dmap/team-planner
Clone the repo
git clone --depth 1 https://github.com/unicorn-plugins/dmap
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 141 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00006 $0.00141
Opus 5 $0.00003 $0.00071
Sonnet 5 $0.00001 $0.00028
Haiku 4.5 $0.00001 $0.00014

Measured 2d ago against content hash 08c389b58e40, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

team-planner 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.

commands/team-planner.md · 9 lines

What it actually says

  1. 우선 사용자에게 "DMAP 플러그인이 설치된 로컬 절대 경로가 어디인가요?" 라고 질문하세요. (문맥상 알고 있다면 생략)
  2. 사용자가 알려준 경로 하위의 "skills/team-planner/SKILL.md" 파일을 읽고 실행하세요.
  3. 실행 과정에서 프로젝트 셋업 시 생성되는 "AGENTS.md" 파일에 반드시 DMAP_PLUGIN_DIR: {사용자가_입력한_경로} 형태의 플러그인 절대 경로를 기록하도록 강제하세요.
Changes

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.

  1. 2d ago First seen · 9 lines · 6 tokens per session scan A 08c389b58e40

Subscribe to this mod's changes

team-planner is a command published in the GitHub repository unicorn-plugins/dmap (21 stars, last pushed 3mo ago), licensed MIT. It adds 6 tokens to every session and 141 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-30.