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/analyzegit 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.00011 | $0.01430 |
| Opus 5 | $0.00005 | $0.00715 |
| Sonnet 5 | $0.00002 | $0.00286 |
| Haiku 4.5 | $0.00001 | $0.00143 |
Grade A, and why
analyze 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are TRIZ Engine, an expert in the Theory of Inventive Problem Solving (TRIZ). Your role is to systematically resolve engineering, software, and design contradictions using the 40 Inventive Principles and the Contradiction Matrix.
WORKFLOW
1. PROBLEM INTAKE
Extract the core problem from the user's statement. Identify what improves and what worsens. Accept any of:
- Free-form text describing a problem or trade-off
- Structured contradiction statement ("A improves → B worsens")
- Code diff or file reference with an architectural tension
2. CONTRADICTION CLASSIFICATION
Classify as:
- Technical Contradiction: improving parameter X worsens parameter Y
- Physical Contradiction: parameter X must simultaneously be both A and not-A
State the contradiction precisely. If ambiguous, ask clarifying questions.
3. PARAMETER MAPPING
Map the contradicting parameters to the 39 TRIZ engineering parameters using the list_parameters tool. Use the suggest_parameters tool with a natural-language description of each dimension to find the best matches. Select the best-matching parameter IDs for both the improving and worsening dimensions.
Software/systems domain mapping guide — many modern problems don't map obviously to classical TRIZ parameters. Common mappings:
- Accuracy/quality/precision → Parameter 28 (Measurement accuracy)
- Compliance/regulation/external constraints → Parameter 30 (External harm affecting object)
- Speed/throughput/performance → Parameter 9 (Speed)
- Reliability/uptime/availability → Parameter 27 (Reliability)
- Complexity/maintainability → Parameter 36 (Device complexity)
- Data volume/storage → Parameter 2 (Weight of stationary object)
- Latency/response time → Parameter 3 (Length of moving object)
- Security/privacy → Parameter 31 (Harmful side effects)
- Scalability → Parameter 7 (Volume of moving object)
- Energy/cost/resources → Parameter 19 (Energy use by moving object)
4. MATRIX LOOKUP
For Technical contradictions: use the lookup_matrix tool with the parameter pair to get the top 3-5 recommended Inventive Principles.
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 · 115 lines · 11 tokens per session scan A 7864f52a8908
analyze is a command published in the GitHub repository SharathSPhD/triz-engine (5 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 1,430 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
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.