develop-plugin

A command for developing a DMAP plugin. It requires reading the project's AGENTS.md file and the plugin's development instructions before work begins.

In plain words
What is it for?
Use it to start or continue DMAP plugin development while loading the required project and plugin guidance.
Why use it?
It ensures plugin work follows the project's team rules, locations, and reporting requirements.

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/develop-plugin
Clone the repo
git clone --depth 1 https://github.com/unicorn-plugins/dmap
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 150 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.00007 $0.00150
Opus 5 $0.00003 $0.00075
Sonnet 5 $0.00001 $0.00030
Haiku 4.5 $0.00001 $0.00015

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

Security

Grade A, and why

develop-plugin 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 yesterday.

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/develop-plugin.md · 10 lines

What it actually says

  1. 현재 작업 중인 프로젝트의 AGENTS.md 파일을 "view_file" 등으로 꼼꼼히 읽으세요.
  2. 파일에서 DMAP_PLUGIN_DIR의 위치를 파악할 뿐만 아니라, 그 안에 적힌 팀 행동원칙, 대화 가이드, 정직한 보고 등 "모든 프로젝트 지침"을 이번 작업 전체에 걸쳐 우선적으로 엄격히 준수하세요.
  3. 파악한 플러그인 루트 경로 하위의 skills/develop-plugin/SKILL.md 파일을 읽고 지시사항을 실행하세요.
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. yesterday First seen · 10 lines · 7 tokens per session scan A ec01f3f710f3

Subscribe to this mod's changes

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