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-build/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-build)<a href="https://agentmods.dev/skills/gevico/cosim-gpu/cosim-gpu-build"><img src="https://agentmods.dev/badge/skills/gevico/cosim-gpu/cosim-gpu-build/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-build"><img src="https://agentmods.dev/badge/skills/gevico/cosim-gpu/cosim-gpu-build.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.00031 | $0.00402 |
| Opus 5.5 | $0.00012 | $0.00161 |
| Sonnet 5.5 | $0.00006 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
cosim-gpu-build 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
Cosim Build
Build simulators through the top-level justfile. The source submodules live
under third_party/, and build outputs stay under the repository's build/
directory.
Build recipes
just dev-image
just build-gem5
just build-qemu
just build-gem5 1 limits gem5 compilation to one job when linking runs out of
memory. The recipes select the Host or development container through
COSIM_ENV.
Source and output paths
| Component | Source | Default output |
|---|---|---|
| gem5 | third_party/gem5/ |
build/gem5/<host-architecture>/VEGA_X86/gem5.opt |
| QEMU | third_party/qemu/ |
build/qemu/qemu-system-<host-architecture> |
GEM5_BUILD_DIR can select another output directory under the repository's
build/. It does not select a different gem5 source tree. Inspect the selected
path with:
just --evaluate gem5_build_dir
Build provenance
Read references/build-policy-and-provenance.md before deciding whether a
binary matches the checked-out sources or accepting build evidence. Read
references/worktree-incremental-build.md when building from an isolated
cosim-gpu worktree.
Use the binary at the selected output path when launching or testing. CI runtime artifacts include a manifest with the source revision, build key and artifact checksums.
Do not invoke scripts/host/build.sh, raw scons, QEMU configure, make, or
Docker build commands directly. Use the corresponding just recipe.
What ships with it
2 files 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.
- 4d ago Changed · -3 lines · -3 tokens per session f191ef963dab
- 9d ago Changed 559b0c37cc95
- 11d ago Changed d787e45feaa6
- 12d ago Changed · -17 lines · -19 tokens per session 86a35ac57cac
- 19d ago First seen · 72 lines · 53 tokens per session scan A 37bf774c7d92
cosim-gpu-build is a skill published in the GitHub repository gevico/cosim-gpu (95 stars, last pushed 4d ago), licensed Apache-2.0. It adds 31 tokens to every session and 402 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-10.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…