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 dayfinggg/openai-codex-agent-skills --skill rust-changegit clone --depth 1 https://github.com/dayfinggg/openai-codex-agent-skillsWrote 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/dayfinggg/openai-codex-agent-skills/rust-change)<a href="https://agentmods.dev/skills/dayfinggg/openai-codex-agent-skills/rust-change"><img src="https://agentmods.dev/badge/skills/dayfinggg/openai-codex-agent-skills/rust-change/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/dayfinggg/openai-codex-agent-skills/rust-change"><img src="https://agentmods.dev/badge/skills/dayfinggg/openai-codex-agent-skills/rust-change.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.00035 | $0.00368 |
| Opus 5.5 | $0.00014 | $0.00147 |
| Sonnet 5.5 | $0.00007 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
rust-change 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 today.
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.
What it actually says
Verify Rust changes against the crate's real configuration and consumers.
- Establish toolchain, edition, MSRV, workspace members, targets, and features from project and CI configuration. Do not use APIs newer than the MSRV without an authorized upgrade.
- Find the public contract, ownership, and error boundary. Do not resolve a borrow-checking failure through large clones or an architectural rewrite without understanding lifetimes.
- For async code, identify the runtime, task owner, cancellation, and held resources. Inspect guards and blocking work across await boundaries. Ending a wait does not always cancel a side effect.
- For unsafe or FFI code, establish the invariant callers must uphold and how it is checked. Minimize the unsafe region and prefer an existing safe interface.
- Check errors and panic on external input. Do not replace expected failure handling with unwrap or expect for convenience. Preserve public trait bounds and Send/Sync semantics.
- Run formatting, appropriate Clippy checks, cargo check, a real build, and relevant tests for material configurations. Use all-features only when those features can coexist.
- For library API changes, check consumers and documentation tests. Use Miri or sanitizers only when the risk and supported environment justify them.
Cargo check does not perform all code generation and does not replace builds or tests. State the tested targets and features when the distinction affects confidence.
Consult Cargo Check, Cargo Features, and the selected async runtime's documentation.
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.
- today First seen · 20 lines · 35 tokens per session scan A afdb083eec33
rust-change is a skill published in the GitHub repository dayfinggg/openai-codex-agent-skills (8 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 368 once invoked, about $0.0001 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-30.
Other skills, from other repositories
neo-rust
Use this skill when writing, refactoring, debugging, or auditing Rust code. Trigger for .rs files, Cargo projects, ownership/borrowing/lifetime issues, Result/Option error handling, unnecessary clone/performance work, unsafe code review, or modern Rust architecture.
raspberry-pi-rust-embedded
Production-grade embedded Rust guidelines for Raspberry Pi (bare-metal nostd and Linux embedded std/rppal/embedded-hal). Use when developing low-latency hardware control apps, embedded Rust drivers, Linux GPIO/SPI/I2C/UART software, real-time interrupt handlers, and memory-safe hardware abstractions.
tauri-rust-and-frontend-desktop
Architectural patterns, security IPC, performance optimization, native integration, and production best practices for building cross-platform desktop applications using Tauri (v2) and Rust with modern web frontends (React, Svelte, Vue). Use when designing, building, or optimizing Tauri desktop apps.
rs-reviewer
Review selected Rust code for ownership, errors, concurrency, async lifecycle, unsafe and FFI contracts, and runtime/API defects using the project's actual toolchain, features, and dependencies.
learn-rust
Use when the user wants to learn Rust interactively by exploring the sessions-chronicle codebase, guided by questions, micro-exercises, and Rust Book references.
scaffold-rust
Scaffold a complete Rust project with CI/CD, release pipeline, and sr.yaml. Uses cargo as the native build system. Loads on top of scaffold-project (run that first for cross-language standard files). Use when creating a new Rust CLI, library, or workspace, or when the user mentions "new Rust project", "cargo init", or…