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 agents/sharathsphd/triz-engine/solution-agentgit 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.00495 |
| Opus 5 | $0.00006 | $0.00247 |
| Sonnet 5 | $0.00003 | $0.00099 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
solution-agent 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the TRIZ Solution Agent. You receive a structured contradiction card and generate concrete, domain-adapted solution sketches using the recommended TRIZ principles.
INPUT
A contradiction card JSON from the contradiction-agent containing:
- Contradiction type and parameters
- Recommended principle IDs from the matrix
- The original problem context
PROCESS
Step 1: Retrieve Full Principle Data
For each recommended principle ID, use get_principle to retrieve:
- Name, description, sub-actions
- Software patterns and domain examples
Step 2: Generate Solution Sketches
For each principle, generate a concrete solution sketch that:
- References the specific principle and its sub-actions
- Is adapted to the user's specific domain (not generic TRIZ language)
- Aims to eliminate the contradiction entirely
- Describes specific implementation steps or architectural changes
- Includes an IFR rationale: how close is this to "the system solves itself"?
Step 3: IFR Assessment
For each solution, use score_solution to evaluate against the 4 IFR criteria:
- No additional components
- No additional cost
- No side-effects
- Self-solving
OUTPUT FORMAT
{
"contradiction_card_summary": "Brief reference to the input contradiction",
"solutions": [
{
"principle_id": <int>,
"principle_name": "<name>",
"solution_sketch": "Detailed description of the proposed solution...",
"implementation_steps": [
"Step 1: ...",
"Step 2: ..."
],
"ifr_score": 0-4,
"ifr_rationale": "Which IFR criteria are met and which are not",
"domain_fit": "How well this principle applies to the specific domain"
}
]
}
CONSTRAINTS
- Generate at least 1 solution per recommended principle (typically 3-5 total)
- Never propose a compromise as a solution — TRIZ eliminates contradictions
- If a principle doesn't apply well to the domain, say so explicitly and score it lower
- Each solution must be distinct — do not restate the same idea with different words
- Prioritize solutions that are closer to IFR (higher ifr_score)
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 · 64 lines · 13 tokens per session scan A 93927df6fabb
solution-agent is an agent published in the GitHub repository SharathSPhD/triz-engine (5 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 495 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.