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 instructions/intel/gpu-ai-skills/agents-mdgit clone --depth 1 https://github.com/intel/gpu-ai-skillsWrote 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/instructions/intel/gpu-ai-skills/agents-md)<a href="https://agentmods.dev/instructions/intel/gpu-ai-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/intel/gpu-ai-skills/agents-md.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.00650 | $0.00650 |
| Opus 5 | $0.00325 | $0.00325 |
| Sonnet 5 | $0.00130 | $0.00130 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade C, and why
gpu-ai-skills AGENTS.md scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -f` of unowned containers, or `rm -rf` outside a workspace path How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Contract
This file documents how a coding agent should consume this repository.
What this repo is
A pack of Agent Skills for
running, benchmarking, profiling, and fixing models on Intel GPUs.
Each skill is a self-contained directory under skills/.
How to discover skills
Read plugins/intel-gpu-ai-skills/skills/<skill>/SKILL.md. The YAML frontmatter has a name and a
description that tells you when to use it. Load the body when the
description matches the user's intent.
If the host agent supports the Claude Code plugin marketplace, prefer
that install path (.claude-plugin/marketplace.json). Otherwise copy
the skill directory into the agent's standard skills location.
What ships vs what is internal
research/ is an internal scratchpad used while authoring. It is
excluded from published archives via .gitattributes (export-ignore).
Skills must not reference paths under research/ — every claim a
skill makes has to be verifiable from public sources or from a
"verify locally" recipe inlined in the skill body.
Conventions in this repo
- Skill names are kebab-case and match the parent directory.
- Skills do not assume a specific orchestrator. They do not depend on Kintsugi, evidence bundles, or any private container runner.
- Skills assume Docker (or a Docker-compatible runtime) and
xpu-smion the host. Where a script needs more, the skill says so incompatibility. - All shell snippets are POSIX
shor explicitlybash. No fish syntax even though the host shell may be fish. - All Intel-specific knobs (image tags,
ZE_AFFINITY_MASK, dtype preferences) live in skills, not in tooling, so they stay current without code changes.
What this pack avoids
ipex-llm,intel-extension-for-pytorch,intel/llm-scaler-vllm. Upstream PyTorch and upstream vLLM are the supported paths.- Hardcoded container names. Skills accept a container name or image tag as input; they do not assume one is already running.
- Destructive operations. Nothing in this pack does
pkill,docker rm -fof unowned containers, orrm -rfoutside a workspace path the user provided.
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 · 61 lines · 650 tokens per session scan C edfa4b532f4c
gpu-ai-skills AGENTS.md is an instructions file published in the GitHub repository intel/gpu-ai-skills (16 stars, last pushed 7d ago), licensed Apache-2.0. It adds 650 tokens to every session, about $0.0032 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.