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/gpt-cmdr/ras-commander/dev_invoke_claude-codenpx skills add gpt-cmdr/ras-commander --skill dev_invoke_claude-codegit clone --depth 1 https://github.com/gpt-cmdr/ras-commanderWhat 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.00163 | $0.01337 |
| Opus 5 | $0.00081 | $0.00668 |
| Sonnet 5 | $0.00033 | $0.00267 |
| Haiku 4.5 | $0.00016 | $0.00134 |
Grade A, and why
dev_invoke_claude-code 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.
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Invoking Claude Code For QAQC
Codex-native provider handoff skill. This is not a shared domain workflow and should not be mirrored into
.claude/skills/. It lets Codex request an independent Claude Code review while keeping shared repo policy inAGENTS.md.
Use this skill when the user explicitly asks Codex to have Claude Code review code, documentation, notebooks, or agent-framework changes.
Safety Rules
- Use Claude as a read-only reviewer by default.
- Do not let Claude edit files, commit, push, install tools, or mutate the worktree.
- Do not overwrite root-level
TASK.mdorOUTPUT.md; those may belong to another handoff. - Put each review in an ignored workspace such as
working/agent-reviews/claude-code/{timestamp}-{slug}/. - Give Claude the same shared repo contract Codex used: nearest
AGENTS.md, relevant localAGENTS.mdfiles, and task-specific files. - Do not use
--dangerously-skip-permissionsunless the user explicitly requests it and the workspace is externally sandboxed.
Handoff Pattern
Create a review workspace:
$reviewDir = "working/agent-reviews/claude-code/20260426-claude-qaqc"
New-Item -ItemType Directory -Force $reviewDir | Out-Null
Write TASK.md in that folder. Include:
- the review target files or directories
- the exact concern or review objective
- the shared instruction files Claude should read first
- a strict read-only constraint
- the expected finding format
Minimum TASK.md shape:
# Claude Code QAQC Review
You are performing an independent read-only QAQC review for ras-commander.
## Read First
1. AGENTS.md
2. The nearest local AGENTS.md files for the target paths
3. docs/development/multi-harness-agent-contract.md when reviewing agent infrastructure
## Target
- path/to/file_or_directory
## Review Focus
- correctness bugs
- behavioral regressions
- missing tests or validation gaps
- security or supply-chain risks, if relevant
## Constraints
- Do not edit files.
- Do not run destructive commands.
- Do not commit or push.
- Write findings first, ordered by severity.
- Include file and line references when possible.
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 · 169 lines · 163 tokens per session scan A 1183c7fc922e
dev_invoke_claude-code is a skill published in the GitHub repository gpt-cmdr/ras-commander (78 stars, last pushed 2d ago), licensed MIT. It adds 163 tokens to every session and 1,337 once invoked, about $0.0008 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-30.
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.