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/anhnguyen0905/codex-mcp/exec-rustnpx skills add anhnguyen0905/codex-mcp --skill exec-rustgit clone --depth 1 https://github.com/anhnguyen0905/codex-mcpWrote 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/anhnguyen0905/codex-mcp/exec-rust)<a href="https://agentmods.dev/skills/anhnguyen0905/codex-mcp/exec-rust"><img src="https://agentmods.dev/badge/skills/anhnguyen0905/codex-mcp/exec-rust.svg" alt="Measured on agentmods" 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 | $0.00035 | $0.00378 |
| Opus 5 | $0.00017 | $0.00189 |
| Sonnet 5 | $0.00007 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
exec-rust 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 4d 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.
What it actually says
Rust Idioms (embed when project is Rust)
Rust standards:
- Errors: return Result<T, E> for fallible functions; no unwrap()/expect()/panic! in library code
(reserve panic for truly unrecoverable invariants). Propagate with ?; model domain errors with
an enum (thiserror if present), wrap sources with context (anyhow only at bin/top level).
- Ownership: borrow (&T/&mut T) over cloning; clone only when a clear owner is needed. No needless
.to_owned()/.clone() to appease the borrow checker — restructure instead.
- Prefer iterators/combinators (map/filter/collect) over index loops; use ? and Option combinators
(map/and_then/ok_or) instead of manual match when clearer.
- Types: newtypes over primitive obsession; derive(Debug, Clone, PartialEq) where sensible; make
illegal states unrepresentable with enums. Accept impl Trait / generics, expose concrete types.
- Concurrency: prefer message passing or the project's async runtime (tokio/async-std) consistently;
Send/Sync only where needed; no blocking calls inside async without spawn_blocking.
- No unsafe unless unavoidable — if used, isolate it, document the invariant it upholds, and justify.
- Follow rustfmt (non-negotiable) and clippy if configured; match the repo's module layout.
- Tests: #[cfg(test)] mod tests with #[test]; table cases via loops or rstest if present; assert
behavior, not internals; use the repo's assertion style.
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.
- 4d ago First seen · 26 lines · 35 tokens per session scan A b410d86bdf5f
exec-rust is a skill published in the GitHub repository anhnguyen0905/codex-mcp (3 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 378 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…