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 skills add d-oit/rust-2026-template --skill triz-solvergit clone --depth 1 https://github.com/d-oit/rust-2026-templateWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/d-oit/rust-2026-template/triz-solver)<a href="https://agentmods.dev/skills/d-oit/rust-2026-template/triz-solver"><img src="https://agentmods.dev/badge/skills/d-oit/rust-2026-template/triz-solver/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/d-oit/rust-2026-template/triz-solver"><img src="https://agentmods.dev/badge/skills/d-oit/rust-2026-template/triz-solver.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What 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.1 | $0.00059 | $0.02103 |
| Opus 5.5 | $0.00024 | $0.00841 |
| Sonnet 5.5 | $0.00012 | $0.00421 |
| Haiku 4.5 | $0.00006 | $0.00210 |
Grade A, and why
triz-solver 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 1mo 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TRIZ Problem Solver — Rust Edition
Systematic innovation methodology for Rust engineering problems.
Core Protocol
Contradiction-First Approach
1. STATE the problem in one sentence
2. IDENTIFY contradiction: "Improving [X] causes [Y] to worsen"
3. CHECK if contradiction is real or apparent
4. RESOLVE using separation principles
5. VALIDATE no new contradictions introduced
Ideal Final Result (IFR)
"The ideal Rust solution delivers all benefits with zero cost, zero unsafe, zero clones"
1. What is the ideal outcome? (no implementation details)
2. What prevents reaching it? (Rust constraints: ownership, lifetimes, traits)
3. Which constraints are real vs assumed?
4. Can the type system enforce correctness without runtime checks?
Inventive Principles (Software Edition)
Principles Applied to Rust
| # | Principle | Rust Analogy | When to Apply |
|---|---|---|---|
| 1 | Segmentation | Split crate, module, function | Monolithic code, complex functions |
| 2 | Taking out | Extract trait, separate mod |
Mixed responsibilities in one type |
| 3 | Local quality | Domain-specific types (Url, UserId) |
Generic String everywhere |
| 4 | Asymmetry | Feature-gated impls, sealed traits | One-size-fits-all antipattern |
| 5 | Merging | Batch operations, reduce round-trips | Excessive function calls, I/O |
| 6 | Universality | Shared trait, polymorphism | Duplicate implementations |
| 7 | Nesting | Cow, lifetime hierarchies |
Flat complex types |
| 9 | Intermediary | Insert an adapter, cache, or queue between two components | Two systems must change in lockstep |
| 12 | Inversion | Pull-based deps, IoC, callbacks | Current push approach failing |
| 13 | Dynamics | Runtime config, feature flags, hot-reload | Static rigid configurations |
| 15 | Feedback | Telemetry, regression test, sensor-driven gate | No way to tell whether a change helped |
| 17 | Another dimension | Add newtype, wrapper, sidecar, index | Impasse at current abstraction level |
| 35 | Parameter change | Retune batch size, shard count, lock width | Algorithm is sound; the tunable is wrong |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · -9 lines 2ab8a1940dda
- 1mo ago Changed 1f5c46455e24
- 2mo ago First seen · 239 lines · 59 tokens per session scan A d3c1cdcebe09
triz-solver is a skill published in the GitHub repository d-oit/rust-2026-template (14 stars, last pushed 3d ago), licensed MIT. It adds 59 tokens to every session and 2,103 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
review-backend
Performs a strict code review of Rust backend code (files, diffs, or snippets). Trigger whenever the user shares backend code (Rust, SQL) and asks for a review, feedback, or says "review this" — including partial snippets.
yada-yada-yada
Enter Seinfeld Mode. Explain programming, debugging, architecture, and code reviews through observational comedy inspired by Seinfeld. Trigger when the user says "what's the deal", festivus, serenity, yada, soup, shrinkage, sponge-worthy, master of my domain, double dip, newman, vandelay, nostrand, constanza or…
fix-issue
Fixes a bug, implements a missing feature, or implements one slice of a larger feature, starting from a GitHub issue link, number, or direct text description. Trigger when the user gives a GitHub issue URL/reference/description and asks to fix, implement, resolve, or work on it.
review-frontend
Performs a strict code review of the Svelte 5 frontend code (files, diffs, or snippets). Trigger whenever the user shares frontend code (Svelte, TypeScript, CSS) and asks for a review, feedback, or says "review this" — including partial snippets.
make-it-so
Enter Star Trek command mode. Use Star Trek terminology naturally while remaining a highly competent engineering officer. Trigger when the user mentions Star Trek, Picard, make it so, engage, stardate, number one, federation, borg, warp, enterprise.
triage-review-finding
Verifies and triages a code review finding (from an AI review, audit doc, or human reviewer) against the actual codebase. Trigger when the user pastes a review comment/finding and asks to check, analyze, or evaluate whether it makes sense.