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/designpipe/exfig/plangit clone --depth 1 https://github.com/DesignPipe/exfigWhat 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.00012 | $0.01054 |
| Opus 5 | $0.00006 | $0.00527 |
| Sonnet 5 | $0.00002 | $0.00211 |
| Haiku 4.5 | $0.00001 | $0.00105 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Planning with Dependencies
Purpose: Analyze a task and break it down into subtasks with explicit dependencies, enabling parallel execution where possible.
Output Format (TOON-like)
Generate plan in this structured format:
command:
name: plan-<task-slug>
purpose: <task description>
version: 1.0
tasks[N]{id,title,description,depends_on,parallel_group,type}:
<id>,<title>,<description>,[deps],[group],[type]
...
execution_order:
phase_1:
parallel: [task_ids that can run in parallel]
phase_2:
sequential: [task_id] # build/test tasks
phase_3:
parallel: [task_ids for fixes if needed]
...
dependency_graph:
<task_id>: [list of task_ids this depends on]
...
Task Types
analysis- Code analysis, research, readingimplementation- Writing new codemodification- Changing existing codebuild- Building project/moduletest- Running testsfix- Fixing issues found by build/testsreview- Code review, validation
Dependency Rules
Critical Rules for Parallel Execution
- Independent tasks (no shared files/modules) can run in parallel
- Build tasks MUST wait for ALL parallel implementation tasks to complete
- Test tasks MUST wait for build to succeed
- Fix tasks MUST wait for test results
- Tasks modifying same file MUST be sequential
Dependency Detection
- Same file modification → sequential
- Same module modification → sequential (unless different files)
- Different modules → parallel possible
- Build depends on → all implementation tasks
- Test depends on → successful build
- Fix depends on → test results
Instructions
-
Analyze the task:
- Read relevant code files mentioned in task
- Identify affected modules/files
- Detect potential conflicts
-
Break down into subtasks:
- Create atomic, independent subtasks where possible
- Identify dependencies between subtasks
- Group parallelizable tasks
-
Generate execution plan:
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.
- yesterday First seen · 145 lines · 12 tokens per session scan A 04c89a81a595
plan is a command published in the GitHub repository DesignPipe/exfig (10 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 1,054 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 commands, from other repositories
figma-apply
피그마 변경을 현재 design/ 브랜치에 반영(커밋·푸시). /figma-start 이후에 사용.
feature
Post a feature to the Features Board on production and write tweets.
worktree
Create a git worktree and start development environment.
commit-all
Group all changes semantically and commit each group separately.
release-mobilewright
Prepare a mobilewright release by updating CHANGELOG.md with the next patch version.
instrument
Generate a comprehensive instrumentation plan for a mobile codebase.