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/extremeclarity/claude-plugins/import-frameworkgit clone --depth 1 https://github.com/extremeclarity/claude-pluginsWhat 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.00010 | $0.01046 |
| Opus 5 | $0.00005 | $0.00523 |
| Sonnet 5 | $0.00002 | $0.00209 |
| Haiku 4.5 | $0.00001 | $0.00105 |
Grade A, and why
import-framework 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.
How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Import Framework
Import frameworks from external files or folders, with supporting terminology and insights.
Input: File path or folder path (as argument)
The Bar
Only import what will clearly help in future sessions.
Every import costs context space in every future session. Before proposing anything, ask:
-
Future Value Test: Will this meaningfully help Claude in future sessions on this project? If you can't articulate a concrete scenario, skip it.
-
Relevance Test: Does it connect to what this project is already about? Unrelated frameworks add noise.
-
Uniqueness Test: Is this already captured in the worldview, or is it general knowledge Claude already has?
Step 0: Get Source Path
If no path was provided as an argument, ask the user for the file or folder path to import from. Do not guess or scan for files.
Process
1. Read Source + Project Context
Source:
- If path is a file: read the file
- If path is a folder: use Glob to find
**/*.mdand**/*.txt, read all - If >2000 lines: warn user and recommend splitting
Project context (for relevance checking):
.worldview/terminology.txt.worldview/principles.txt.worldview/frameworks/index.txt(index only, not full frameworks)
2. Detect Candidate Frameworks
Scan source for structured knowledge that could become frameworks:
- Decision trees / evaluation criteria
- Multi-step processes / workflows
- Mental models with clear structure
- Comparison matrices / trade-off analyses
- Causal models / diagnostic frameworks
For each candidate, apply the bar:
- Duplicate check: Does it already exist in frameworks index?
- Relevance check: Does it connect to project terminology, principles, or existing frameworks?
- Future value check: Will having this framework change Claude's approach in future sessions?
Skip anything that doesn't clearly pass all three.
3. Extract Supporting Items
For each candidate framework, extract:
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 · 135 lines · 10 tokens per session scan A f22a89ac0f40
import-framework is a command published in the GitHub repository extremeclarity/claude-plugins (4 stars, last pushed 6mo ago), licensed MIT. It adds 10 tokens to every session and 1,046 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.