Borrowing it
Nothing to install: this file belongs to gevico/cosim-gpu. 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/gevico/cosim-gpu/main/.agents/skills/cosim-gpu-codex-review/SKILL.mdgit clone --depth 1 https://github.com/gevico/cosim-gpuWrote 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/gevico/cosim-gpu/cosim-gpu-codex-review)<a href="https://agentmods.dev/skills/gevico/cosim-gpu/cosim-gpu-codex-review"><img src="https://agentmods.dev/badge/skills/gevico/cosim-gpu/cosim-gpu-codex-review/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/gevico/cosim-gpu/cosim-gpu-codex-review"><img src="https://agentmods.dev/badge/skills/gevico/cosim-gpu/cosim-gpu-codex-review.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.00058 | $0.00655 |
| Opus 5.5 | $0.00023 | $0.00262 |
| Sonnet 5.5 | $0.00012 | $0.00131 |
| Haiku 4.5 | $0.00006 | $0.00065 |
Grade A, and why
cosim-gpu-codex-review 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 19d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Review
Use an independent AI reviewer for bounded technical review, investigation, or
design critique. This skill owns delegation mechanics only. Review policy shared
with cosim-gpu-review and cosim-gpu-rlcr-loop lives in
../cosim-gpu-review/references/review/independent-review-contract.md; read it
before adversarial review delegation.
Scope
Use this skill for:
- adversarial code review from a written brief
- single-file or subsystem investigation with explicit questions
- design critique of a proposed local change
- second opinion when the main investigation is stuck
Do not delegate user interaction, task scoping, build commands, test commands, or final verification. The main agent owns integration and evidence acceptance.
Assignment Template
Each assignment must be self-contained:
# Target
Exact files, symbols, base reference, current HEAD, and non-goals.
# Change Or Review Question
For review: dimensions to inspect and exact diff commands.
For investigation: symptom, search scope, and questions.
For design: current code, constraints, and rejected directions if artifact-backed.
# Acceptance
Expected output format, severity labels, and required evidence.
No project-wide build, test, or lint commands.
Implementation-oriented assignments must require current HEAD as the edit
base, diff-scoped formatting only, and no whole-file formatter churn unless the
task is explicitly formatting-only.
Adversarial Review Prompt
Prepare the review brief through cosim-gpu-review or cosim-gpu-rlcr-loop.
The sub-agent prompt points to that brief and may include exact scoped diff
commands. It must not include the implementer's theory, desired result, or
dialogue summary.
For cosim-specific prompts, use
references/cosim-gpu-review-prompts.md when the touched subsystem matches
interrupt handling, PM4, cache or TLB behavior, HSA completion signals, or
similar GPU model paths.
Evidence Recording
Save every consultation under the active task workspace:
What ships with it
1 file 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.
- 19d ago First seen · 82 lines · 58 tokens per session scan A 7ba0665d89b1
cosim-gpu-codex-review is a skill published in the GitHub repository gevico/cosim-gpu (95 stars, last pushed 4d ago), licensed Apache-2.0. It adds 58 tokens to every session and 655 once invoked, about $0.0002 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-10.
Other skills, from other repositories
sync-bridge
Reviews and guides Chromium Sync Model API (DataTypeSyncBridge) implementations, including DataTypeStore persistence and forwards/backwards compatibility for sync specifics. Use when implementing or reviewing a DataTypeSyncBridge subclass, DataTypeStore usage, sync metadata persistence, conflict resolution, or…
sync-model-processor
Reviews changes to Chromium Sync model internals in components/sync/model/, including ClientTagBasedDataTypeProcessor, ClientTagBasedRemoteUpdateHandler, ProcessorEntity, ProcessorEntityMetadata, and ProcessorEntityTracker. Use when modifying or reviewing processor state transitions, entity metadata tracking, conflict…
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
gsd-ns-review
Invoke this Pi skill with /skill:gsd-ns-review.
gitnexus
A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…