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/ailvenliu/agent-foundry/gpu-cinpx skills add AilvenLIU/agent-foundry --skill gpu-cigit clone --depth 1 https://github.com/AilvenLIU/agent-foundryWrote 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/ailvenliu/agent-foundry/gpu-ci)<a href="https://agentmods.dev/skills/ailvenliu/agent-foundry/gpu-ci"><img src="https://agentmods.dev/badge/skills/ailvenliu/agent-foundry/gpu-ci.svg" alt="Measured on agentmods" 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 | $0.00051 | $0.01858 |
| Opus 5 | $0.00026 | $0.00929 |
| Sonnet 5 | $0.00010 | $0.00372 |
| Haiku 4.5 | $0.00005 | $0.00186 |
Grade A, and why
gpu-ci 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 4d ago First seen · 184 lines · 51 tokens per session scan A a8e1f0348f98
gpu-ci is a skill published in the GitHub repository AilvenLIU/agent-foundry (5 stars, last pushed 2d ago), with no licence file. It adds 51 tokens to every session and 1,858 once invoked, about $0.0003 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
setup-action
Sets up GitHub Actions for ESP32 projects — building ESP-IDF firmware in a pinned container, taking the version from the git tag, proving a published image is the variant it claims to be, and publishing artefacts and a release when a tag is pushed. Also covers the pre-merge gate: lint plus the tests a hosted runner…
create-module
Create a new AirStack module repository by hand — author the thin module.yaml manifest, lay out colcon packages with canonical-default launch args (never remaps), add teststack/ and CI, and validate with tools/validatemodule.py. Use when packaging a capability (planner, estimator, sim extension, vehicle data) as a…
ha-esphome-ci-scaffold
Scaffolds the CI that validates an ESPHome fleet per spec/ha/esphome-project-structure §Validation — a pull-request workflow running esphome config for every device file on every change rather than only the diff, because a package edit breaks devices nobody touched, plus a scheduled or pre-release job for the far…
yocto-agent-suite
One-router Yocto Project skill suite for AI coding agents. Use when a request mentions Yocto, OpenEmbedded, Poky, BitBake, embedded Linux builds, BSPs, board flashing, QEMU boot tests, CI/release automation, security hardening, CVE review, secure boot, OTA updates, firewall policy, or when the right specialized Yocto…
yocto-ci-kas-build
Official-doc-first Yocto CI, kas, and reproducible build workflow support for AI coding agents. Use when creating or modifying kas YAML files, CI pipelines, containerized Yocto builds, shared DLDIR or SSTATEDIR caching, build matrix jobs, smoke builds, artifact publishing, reproducibility checks, or repository…
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…