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/nvidia/elements/audit-cinpx skills add NVIDIA/elements --skill audit-cigit clone --depth 1 https://github.com/NVIDIA/elementsWhat 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.00078 | $0.01411 |
| Opus 5 | $0.00039 | $0.00705 |
| Sonnet 5 | $0.00016 | $0.00282 |
| Haiku 4.5 | $0.00008 | $0.00141 |
Grade A, and why
audit-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 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit CI
Produce a repeatable cold-CI profile, explain what controls wall-clock completion, and turn the evidence into prioritized, testable recommendations.
Required context
- Read the repository
AGENTS.md. - Read
projects/internals/BUILD.md. - Inspect the current root
ci:profilescript andprojects/internals/ci/ci-profile.js. Treat the script as the profiling source of truth. - Read a project's
DEVELOPMENT.mdbefore running project-specific commands when that file exists.
Do not copy profiling logic into this skill. Update the repository profiler when its behavior needs to change.
Choose the workflow
- Run a new profile when the user asks to rerun, benchmark current changes, refresh an audit, or verify an optimization.
- Analyze existing
.metrics/ci-profile.{json,md}artifacts without rerunning when the user asks only for interpretation and the artifacts match the intended commit and worktree state. - Create recommendations without implementing them unless the user also asks for the changes.
Profile safely
Run all repository commands through mise.
-
Inspect
git status --short. -
Preview ignored files that reset would delete with
git clean -ndX. -
Stop and ask before profiling if that preview includes user data, local assets, secrets, or other non-reproducible files. The profiler runs
pnpm run ci:reset, which deletes ignored files and reinstalls dependencies before every sample. -
Never stash, commit, discard, or clean tracked changes merely to make the profiler accept the worktree.
-
Use the clean command when the worktree is clean:
mise exec -- pnpm run ci:profile -
When the dirty changes are the intentional subject of the audit, preserve them and run:
CI_PROFILE_ALLOW_DIRTY=1 mise exec -- pnpm run ci:profileRecord the dirty-worktree condition in the report. Do not use this override for unrelated or unexplained changes.
Allow all three cold samples to finish. Dependency installation or browser setup can require network access. If a run fails, inspect the copied .metrics/ci-profile-run-*.log and reset logs, report the incomplete profile, and do not invent missing samples.
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.
- 2d ago First seen · 139 lines · 78 tokens per session scan A e8050249f9a1
audit-ci is a skill published in the GitHub repository NVIDIA/elements (83 stars, last pushed 2d ago), licensed Apache-2.0. It adds 78 tokens to every session and 1,411 once invoked, about $0.0004 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-30.
Other skills, from other repositories
design-doc-interviewer
Interview the user to turn a proposed product/engineering change into a structured design document. Use when the user asks to be interviewed, wants help clarifying a design, or wants a design doc produced from Q&A. Emphasize numbered questions (few at a time), capture requirements/constraints/UX/data/logic/testing…
ideate
Capture and document a new idea in this repo. Use when the user says things like "help me brainstorm", "I have an idea", or "let's capture this for the future" and wants it recorded in design/ideas/ with a summary, supporting research (repo context + web if useful), and a sketch.
beui
Pick and install beUI (@beui) animated React components from the shadcn registry. Use when building motion UI, agent/chat interfaces, toasts, docks, bottom sheets, drawers, popovers, sliders, loaders, 404 pages, or any beui.dev component. Maps user intent to exact @beui install slugs instead of inventing custom…
beui-pro
Choose, inspect, install, and compose licensed beUI Pro premium React blocks from the authenticated shadcn registry. Use when building or improving landing pages with beUI Pro, installing @beui-pro items, selecting premium heroes, features, pricing, social proof, CTAs, navigation, footers, or other page sections, or…
ui-development
Build UI pages and extensions for Falcon Foundry apps using React or Vue with the Shoelace design system and Foundry-JS. TRIGGER when user asks to "create a UI page", "build a UI extension", "add a Shoelace component", "call an API from the UI", runs foundry ui pages create or foundry ui run, or needs help with Vite…
vue-application-structure
Establishes or reviews the directory layout, component conventions, composable design, Pinia store structure, and Vue Router configuration for a Vue 3 TypeScript application. Invoked when the user asks to structure a Vue app, set up the project layout, or review Vue architecture.