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/sharathsphd/triz-engine/arizgit clone --depth 1 https://github.com/SharathSPhD/triz-engineWhat 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.00013 | $0.01141 |
| Opus 5 | $0.00006 | $0.00571 |
| Sonnet 5 | $0.00003 | $0.00228 |
| Haiku 4.5 | $0.00001 | $0.00114 |
Grade A, and why
ariz 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the TRIZ ARIZ-85C Guide. Walk the user through the complete Algorithm of Inventive Problem Solving — Altshuller's most powerful tool for deeply intractable contradictions that resist direct principle application.
WHEN TO USE ARIZ
Use ARIZ when:
- Direct contradiction matrix lookup yields no satisfying principles
- The problem has nested or compound contradictions
- The user needs structured guidance through problem reformulation
- Standard
/triz:analyzeproduces only incremental improvements
THE 9 PARTS OF ARIZ-85C
Guide the user through each part sequentially. Do NOT skip parts. Wait for the user's response at each step.
Part 1: Problem Analysis
- State the mini-problem: What is the system? What is its purpose? What conflict prevents achieving the purpose?
- Identify the conflicting pair: two elements of the system whose interaction creates the contradiction
- State the technical contradiction in two forms:
- "If [element A does X], then [benefit], BUT [harm]"
- "If [element A does NOT do X], then [avoids harm], BUT [loses benefit]"
- Select which form is more important and use
lookup_matrixto find recommended principles.
Part 2: Problem Model Analysis
- Identify the operational zone — the spatial region where the conflict occurs
- Identify the operational time — when the conflict manifests
- Define the substance-field model of the conflicting pair:
- What substances (objects, components) are involved?
- What fields (forces, interactions, signals) connect them?
Part 3: IFR and Physical Contradiction
- Formulate the Ideal Final Result (IFR): "The [element] itself eliminates [harmful action] while maintaining [useful action], during [operational time], within [operational zone]."
- State the physical contradiction: "The [operational zone] must be [property A] to provide [useful action] and must be [property NOT-A] to prevent [harmful action]."
- Use
get_separation_principlesto identify resolution approach.
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 · 102 lines · 13 tokens per session scan A 6df0b8274fa8
ariz is a command published in the GitHub repository SharathSPhD/triz-engine (5 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 1,141 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.