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 skills add Dogacel/auto-gpu-kernel --skill build-harnessgit clone --depth 1 https://github.com/Dogacel/auto-gpu-kernelWrote 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/dogacel/auto-gpu-kernel/build-harness)<a href="https://agentmods.dev/skills/dogacel/auto-gpu-kernel/build-harness"><img src="https://agentmods.dev/badge/skills/dogacel/auto-gpu-kernel/build-harness/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/dogacel/auto-gpu-kernel/build-harness"><img src="https://agentmods.dev/badge/skills/dogacel/auto-gpu-kernel/build-harness.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.00029 | $0.00985 |
| Opus 5 | $0.00015 | $0.00492 |
| Sonnet 5 | $0.00006 | $0.00197 |
| Haiku 4.5 | $0.00003 | $0.00098 |
Grade A, and why
build-harness 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 2d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
build-harness
Read the verbal brief in config.toml and AGENTS.md, inspect the untouched target
repository, and generate the two adapters kbench needs. Do not optimize the target yet.
Boundary
The target clone is read-only during this turn. Record its HEAD and
git status --porcelain first. You may read source, tests, documentation, build files,
and history, and run existing commands. Do not edit tracked files, commit, switch
branches, or run tools that rewrite lockfiles. Remove untracked files you create and
finish with the same HEAD and status.
Write only under harness/ and .omp/. Never access or modify auto-gpu-kernel itself.
Understand the task
Determine from the brief and repository:
- the target code the optimizer may edit and the public behavior it must preserve;
- the cheapest meaningful correctness check and the comprehensive correctness check;
- the cheap measurement useful during iteration and the representative full metric;
- the metric unit and whether lower or higher is better;
- required setup, warmup, synchronization, seeds, caches, and noise controls.
Prefer repo-native tests and benchmarks. The adapters may wrap any local command, but
they must judge the target repository passed via --repo, not a copied implementation.
Generate harness/validate.py
It must accept exactly these common arguments:
--repo PATH
--mode quick|full
--output PATH
Kbench runs both scripts with the candidate checkout as the working directory (the
clone, or a temporary worktree during kbench ab) — always use --repo, never assume
the clone path. It exports KBENCH_ROOT (the project) and KBENCH_HARNESS (the
harness/ directory); locate fixtures via KBENCH_HARNESS, never by relative path.
Each script is killed after 30 minutes in quick mode and 60 minutes in full mode.
Anything the scripts write into the candidate checkout that git does not already ignore
(build outputs, caches; bytecode is already disabled) is detected as a candidate change
and fails the run — keep scratch under --output's directory or a temp dir.
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.
- 2d ago First seen · 107 lines · 29 tokens per session scan A ee9d630d0fbc
build-harness is a skill published in the GitHub repository Dogacel/auto-gpu-kernel (161 stars, last pushed 2d ago), licensed Apache-2.0. It adds 29 tokens to every session and 985 once invoked, about $0.0001 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-09-13.
Other skills, from other repositories
review
Structured PR review for pygraphistry. Input: PR number/branch (default current branch PR). Output: findings and convergence artifacts under plans/ /. Method: multi-wave, evidence-first review across spec, correctness, tests, security, code quality, DRY, concurrency, performance, architecture, operability, and…
test-amplification
Methodical bug-driven test amplification for pygraphistry features. Use when hardening a feature area via user-workflow exploration, 5-Whys retrospectives, bug-taxonomy derivation, concrete test planning, implementation, and safety-gated validation.
testing
Writing frontend tests for the nvcf-ui app — Vitest, Testing Library, MSW, and project-specific render helpers. Use when creating test files, writing component tests, setting up MSW handlers in tests, deciding which render helper to use, or when the user is adding or modifying a UI component and hasn't mentioned tests…
cuda-kernel-optimizer
Use when optimizing or diagnosing GPU workload performance with CUDA, CUTLASS, Triton, PyTorch, vLLM or TensorRT-LLM; interpreting NCU, Nsys or PyTorch Profiler evidence; or preparing the workload and correctness checks for such optimization. General coding, skill maintenance and conceptual GPU questions do not…
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".