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/morpho-org/sdks/extract-plangit clone --depth 1 https://github.com/morpho-org/sdksWhat 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.00000 | $0.02658 |
| Opus 5 | $0.00000 | $0.01329 |
| Sonnet 5 | $0.00000 | $0.00532 |
| Haiku 4.5 | $0.00000 | $0.00266 |
Grade A, and why
extract-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 today.
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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
extract-plan
Read a technical document (TIB, RFC, design doc, etc.) and generate a Linear project plan with milestones and implementation issues from it.
Arguments
$ARGUMENTSshould contain:<doc-file-path> [linear-project-name-or-id]- Example:
/extract-plan TIB/TIB-2026-04-30-blue-sdk-observability.md "Blue SDK Observability"
Instructions
You are converting a technical document into an actionable Linear project plan with milestones and issues. The goal is to bridge the gap between a written decision or design and trackable implementation work.
The input document may be a TIB, RFC, design doc, or any structured technical document that describes a decision, approach, and/or implementation plan.
Step 1: Parse Arguments
Check $ARGUMENTS:
- If two arguments are provided, treat the first as the document file path and the second as the Linear project name or ID.
- If one argument is provided, treat it as the document file path and ask the user for the target Linear project.
- If no arguments are provided, ask:
- "Which document should I convert? (file path)"
- "Which Linear project should the issues be created in? (project name or ID, or 'new' to create one)"
If the user says "new", you will create the project in Step 5.
Step 2: Read and Parse the Document
Read the document and extract structured information. Adapt to whatever sections and format are present — the following are common patterns, not requirements:
| Common Section | What to extract |
|---|---|
| Metadata | Status, Date, Author, Scope |
| Context / Background | Problem statement and motivation — becomes project description |
| Decision Drivers / Goals | Constraints and priorities — informs issue prioritization |
| Decision / Approach | The chosen approach and its subsections — primary source for tasks |
| Implementation Phases | Phase breakdown — maps directly to milestones |
| Consequences / Tradeoffs | Positive/Negative/Neutral — informs acceptance criteria |
| Future Considerations | Items explicitly deferred — may become backlog issues |
| References | Links and prior art — attached to relevant issues |
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.
- today First seen · 276 lines · 0 tokens per session scan A ed94f579b025
extract-plan is a command published in the GitHub repository morpho-org/sdks (40 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,658 tokens. 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-09-01.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
project-recap
Generate a visual project recap for context switching.
speckit.taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
ado-pull
Pull latest changes from Azure DevOps (like git pull). Supports increment, project, or full living docs sync.
issue-amend
Re-snapshot the active issue's scope from the spec, clear verified and reviewed receipts, and record the change as a permanent amendment.
guide
You are a triage agent who continuously prioritizes loom:issue issues by applying loom:urgent to the top 3 priorities.