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-rubynpx skills add anhnguyen0905/codex-mcp --skill exec-rubygit clone --depth 1 https://github.com/anhnguyen0905/codex-mcpWhat 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.00034 | $0.00344 |
| Opus 5 | $0.00017 | $0.00172 |
| Sonnet 5 | $0.00007 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
exec-ruby 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 2d 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
Ruby Idioms (embed when project is Ruby)
Ruby standards:
- Follow the community style guide / the repo's RuboCop config: snake_case methods/vars, CamelCase
classes, SCREAMING_SNAKE constants; two-space indent; guard clauses over nested conditionals.
- Errors: raise specific StandardError subclasses with messages; rescue the narrowest class you can
handle; never rescue Exception broadly; use ensure for cleanup; avoid rescue => e that swallows.
- Prefer expressive enumerables (map/select/reduce/each_with_object) over manual loops; use safe
navigation (&.) and fetch with defaults over silent nil; freeze constants and string literals
where the project does (# frozen_string_literal: true).
- Keep methods short and single-purpose; extract private methods; avoid mutating shared state and
method args unless the API intends it (bang methods signal mutation).
- Rails (if present): use its idioms — strong params, validations and scopes on models, avoid N+1
with includes/eager_load, service objects for complex logic, migrations for schema. Never
interpolate input into SQL — use the query interface or parameterized where.
- Add gems only via the Gemfile; respect the existing dependency and load-path conventions.
- Tests: RSpec or Minitest to match the repo; describe/context/it with behavior-focused names;
arrange-act-assert; use factories/fixtures the project already uses.
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.
- 2d ago First seen · 26 lines · 34 tokens per session scan A a8bd2ee7bb82
exec-ruby is a skill published in the GitHub repository anhnguyen0905/codex-mcp (3 stars, last pushed 10d ago), licensed MIT. It adds 34 tokens to every session and 344 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.