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 skills/d-oit/rust-2026-template/triz-solvernpx skills add d-oit/rust-2026-template --skill triz-solvergit clone --depth 1 https://github.com/d-oit/rust-2026-templateWhat 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.00059 | $0.02121 |
| Opus 5 | $0.00030 | $0.01060 |
| Sonnet 5 | $0.00012 | $0.00424 |
| Haiku 4.5 | $0.00006 | $0.00212 |
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 3d 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 — 239 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.
When to Use
- Complex Rust problems with apparent trade-offs
- System design contradictions (improving X worsens Y)
- Architecture refactoring decisions in a workspace
- Seeking innovative solutions beyond incremental improvement
- Agent instruction optimization
- Stuck on borrow-checker, lifetime, or trait-bound conflicts
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?
40 Inventive Principles (Software Edition)
Top 10 for 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 |
| 12 | Inversion | Pull-based deps, IoC, callbacks | Current push approach failing |
| 13 | Dynamics | Runtime config, feature flags, hot-reload | Static rigid configurations |
| 17 | Another dimension | Add newtype, wrapper, sidecar | Impasse at current abstraction level |
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.
- 3d 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 (10 stars, last pushed 3d ago), licensed MIT. It adds 59 tokens to every session and 2,121 once invoked, about $0.0003 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 skills, from other repositories
create-wot-ui-theme
为 wot-ui 生成单文件主题 SCSS，并在用户明确要求接入时追加 App.vue 的 @use。当用户要做品牌主题、语义变量落地、单文件主题接入时使用。.
starter-cleaner
将 wot-starter v2 模板精简为最小可开发状态，移除文档、演示分包、生成文件和 monorepo 配置，并同步清理相关 Vite 与 package.json 配置。用户要求“清理模板”“移除示例”“生成最小模板”“精简 wot-starter v2”时使用。.
wot-ui-cli
回答、使用、调试 @wot-ui/cli 时使用。关键词：wot、@wot-ui/cli、CLI、MCP、doctor、usage、lint、list、info、doc、demo、token、changelog、extract、wot mcp。适用于命令查询、参数说明、MCP 接入、本地调试、数据提取与 open-wot 仓库维护。.
commit
Use when 使用者要求把工作區的變更寫進版本歷史，不論用詞是 commit、提交、送進 git 還是「整理一下」；需要拆成多筆時同樣適用。NOT for 把 clade 改動散播到 consumer（走 /clade-publish），NOT for 建 / 合併 worktree（走 /wt）。.
better-auth-security-best-practices
Configure rate limiting, manage auth secrets, set up CSRF protection, define trusted origins, secure sessions and cookies, encrypt OAuth tokens, track IP addresses, and implement audit logging for Better Auth. Use when users need to secure their auth setup, prevent brute force attacks, or harden a Better Auth…
better-auth-best-practices
Configure Better Auth server and client, set up database adapters, manage sessions, add plugins, and handle environment variables. Use when users mention Better Auth, betterauth, auth.ts, or need to set up TypeScript authentication with email/password, OAuth, or plugin configuration.