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-repo-maintenance/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-repo-maintenance)<a href="https://agentmods.dev/skills/gevico/cosim-gpu/cosim-gpu-repo-maintenance"><img src="https://agentmods.dev/badge/skills/gevico/cosim-gpu/cosim-gpu-repo-maintenance/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-repo-maintenance"><img src="https://agentmods.dev/badge/skills/gevico/cosim-gpu/cosim-gpu-repo-maintenance.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.00000 | $0.00818 |
| Opus 5.5 | $0.00000 | $0.00327 |
| Sonnet 5.5 | $0.00000 | $0.00164 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
cosim-gpu-repo-maintenance 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 12d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cosim Repo Maintenance
Use this skill for repository hygiene in the cosim-gpu repository when the task does not need cosim build, launch, test, debug, review, or RLCR evidence.
Examples:
- locate or update a submodule under
third_party/, or edit the vendored.agentsskill files - split a large local commit
- rewrite local unpushed commits for better topic boundaries
- audit skill files for sensitive literals or unwanted coupling
- validate skill routing after skill instruction changes
- inspect staged, unstaged, and untracked files before committing
- keep logs, artifacts, build outputs, and scratch files out of history
- verify commit author and
Signed-off-by - update ignore rules for generated outputs
Do not use cosim-gpu-flow-plan for ordinary repository maintenance. If the
task starts requiring cosim test evidence, switch to the matching cosim domain
skill.
General Git Practice
These are general rules, not project-specific behavior:
- Inspect before changing:
git status --short,git diff --stat,git diff --cached --stat, and submodule status when relevant. - Keep commits topic-scoped and reviewable.
- Do not include unrelated working-tree changes.
- Do not rewrite commits that may already be shared unless the user explicitly asks.
- Prefer path-limited
git addandgit commitover broad staging in a dirty tree. - Never use destructive checkout or reset commands to discard unknown changes without explicit user direction.
Project-Specific Rules
Read references/cosim-gpu-repo-policy.md before changing submodule pointers,
editing skill files, or preparing project commits.
Maintenance Workflow
-
Record repository state:
git status --short git submodule status git diff --stat git diff --cached --stat -
Classify changes by owner:
- top-level repository files, including vendored
.agentsskills third_party/gem5source submodulethird_party/gem5-resourcesresource submodulethird_party/qemusource submodule- generated artifacts or local scratch
- top-level repository files, including vendored
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.
- 12d ago Changed · +1 lines 2f0eddbc4ea9
- 19d ago First seen · 98 lines · 0 tokens per session scan A ef2aca3c3b40
cosim-gpu-repo-maintenance is a skill published in the GitHub repository gevico/cosim-gpu (95 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 818 tokens. 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…