Borrowing it
Nothing to install: this file belongs to saschb2b/okf-studio. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/saschb2b/okf-studio/main/.agents/skills/tauri-stinky/SKILL.mdgit clone --depth 1 https://github.com/saschb2b/okf-studioWrote 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/saschb2b/okf-studio/tauri-stinky)<a href="https://agentmods.dev/skills/saschb2b/okf-studio/tauri-stinky"><img src="https://agentmods.dev/badge/skills/saschb2b/okf-studio/tauri-stinky/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/saschb2b/okf-studio/tauri-stinky"><img src="https://agentmods.dev/badge/skills/saschb2b/okf-studio/tauri-stinky.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00214 | $0.02372 |
| Opus 5.5 | $0.00086 | $0.00949 |
| Sonnet 5.5 | $0.00043 | $0.00474 |
| Haiku 4.5 | $0.00021 | $0.00237 |
Grade A, and why
tauri-stinky 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tauri Stinky
A holistic code-smell detector and quality gate for Rust and Tauri. It exists as a counterweight, agents trained mostly on frontend code write Rust confidently and at volume, and the volume is where the smells hide. It finds the patterns that make a crate, a command, or the IPC boundary hard to read, reason about, and trust, explains the cost of each, and proposes a concrete fix. The full catalogs with detection signals, fixes, exceptions, and sources are in rust-catalog.md and tauri-catalog.md; read the relevant one before running a scan.
It defers neighboring concerns to sibling skills so it does not duplicate them: React component, hook, and TypeScript smells on the frontend half to react-stinky, and color literals to theme-colors. If those are not installed, note the finding in one line and move on. Everything about Rust discipline, the Tauri shell, and the boundary between them is in scope.
Targets Tauri v2. On a v1 project, say so and adapt the Tauri-layer advice rather than prescribing v2 config verbatim.
What it sniffs for
Thirteen pillars, 57 categories. Detection signals, fixes, and sources live in the two catalogs.
Rust discipline (rust-catalog.md):
- Error handling and panics.
unwrapin production paths,Result<T, String>and message-substring matching, swallowed results, context-free errors, panic as control flow, catch-all match arms. - Ownership and allocation. Clones that appease the borrow checker,
&Stringparams, needless collects, theArc<Mutex<T>>reflex, index loops. - Type design. Stringly-typed domains, bool blindness, interchangeable primitive ids, representable impossible states, leaky constructors.
- Modules, API, and dependencies. God modules,
pubsprawl, version drift, a dependency for a function. - Async correctness. Blocking calls on the runtime, guards held across
.await, detached tasks that swallow errors,block_onbridges, needlessasync. - Overgeneration and slop (the counterweight pillar). Dead code silenced instead of deleted, speculative traits and layers, reinvented std, comment noise, defensive theater, verbose happy paths.
- Unsafe, lints, and tests. Unjustified
unsafe, blanket lint suppression, untested pure cores and unguarded boundary logic.
What ships with it
10 files 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 · 112 lines · 214 tokens per session scan A b7210b20d62f
tauri-stinky is a skill published in the GitHub repository saschb2b/okf-studio (47 stars, last pushed yesterday), licensed MIT. It adds 214 tokens to every session and 2,372 once invoked, about $0.0009 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-10-23.
Other skills, from other repositories
potpie-cli
Use when the task is centered on running, explaining, configuring, or troubleshooting the potpie command: doctor, login, pot management, source registration, resolve/search/record, graph workbench reads/writes, resource (document payload) commands, and pot scope behavior.
potpie-debug-memory
Use while debugging or troubleshooting failures, flaky tests, incidents, production alerts, CI failures, local dev setup issues, repeated bugs, prior fixes, failed attempts, and verification history.
rubber-duck
Adversarial "rubber duck" review that turns explaining-out-loud into a hallucination check. The main session is the PRESENTER (it did the work — a design doc, investigation, or analysis — and holds the real reasoning) and reconstructs the topic to a LISTENER — a spawned subagent pinned to a DIFFERENT-vendor model that…
windows-compat
Audit and harden this Rust repo (code-graph-mcp) for Windows correctness: path-spelling drift between producers, the 32,767-char command-line cap, index-key mismatches, and path predicates that assume one ecosystem's layout. Use whenever touching code that builds, compares, prints, or stores a filesystem path; that…
worth-fix
A verification and decision-making guide for checking whether bug reports, claims, proposals, or refactoring ideas are true and worth acting on.
tauri-expert
Expert in Tauri framework, Rust backend, web frontend integration, and lightweight desktop applications. Use when the user mentions desktop, Rust, web, cross platform, or performance, or when the task involves Tauri Architecture, Tauri vs Electron, Core Components, or Security Features.