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/guidance-build-systemnpx skills add NVIDIA/elements --skill guidance-build-systemgit 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.00101 | $0.00873 |
| Opus 5 | $0.00051 | $0.00436 |
| Sonnet 5 | $0.00020 | $0.00175 |
| Haiku 4.5 | $0.00010 | $0.00087 |
Grade A, and why
guidance-build 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 3d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guidance Build System
You MUST review the build system documentation before modifying build configurations or troubleshooting build issues.
When to Use This Skill
- Optimizing build performance and parallelization
- Understanding Wireit task dependencies
- Troubleshooting build failures or cache issues
- Adding new build tasks to projects
- Configuring build orchestration across packages
- Understanding CI/CD build pipeline
Quick Reference
Common Commands
# Full CI locally (lint, build, test):same as CI pipeline
pnpm run ci
# Clean everything (node_modules, dist, .wireit caches)
pnpm run ci:reset
# Build a single project
cd projects/core && pnpm run build
# Force that project's Wireit scripts to rerun
mise exec -- git clean -dfX -- .wireit
mise exec -- pnpm run build
# Dev mode with watch
cd projects/core && pnpm run dev
Wireit Basics
Wireit configs live in each project's package.json under the wireit key. Each task declares:
command:the shell command to rundependencies:other wireit tasks that must complete first (can be cross-package)files:input file globs for cache invalidationoutput:output file globs that get cached
Wireit skips tasks whose inputs have not changed since the last run. WIREIT_CACHE=none turns off output caching but does not bypass this incremental freshness check. To force a rerun, run mise exec -- git clean -dfX -- .wireit from the target project directory before invoking the project script.
Dependency Patterns
Cross-package dependencies use the <package>:<script> format:
{
"wireit": {
"build": {
"dependencies": ["../themes:build", "../styles:build"],
"command": "vite build",
"files": ["src/**/*", "tsconfig.json"],
"output": ["dist/**"]
}
}
}
Troubleshooting Build Failures
| Symptom | Fix |
|---|---|
| Stale cache causing wrong output | Clean .wireit/ in the affected project, then rebuild |
| "Cannot find module" after package changes | Run pnpm i --frozen-lockfile to re-link workspaces |
| TypeScript errors after dependency update | Rebuild dependencies first: cd projects/themes && pnpm run build |
| CI passes locally but fails in pipeline | Check Node version (node -v should match .nvmrc) and pnpm version |
| Full reset | pnpm run ci:reset && pnpm i --frozen-lockfile && pnpm run ci |
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.
- 3d ago First seen · 98 lines · 101 tokens per session scan A e9cfafef407f
guidance-build is a skill published in the GitHub repository NVIDIA/elements (83 stars, last pushed 3d ago), licensed Apache-2.0. It adds 101 tokens to every session and 873 once invoked, about $0.0005 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
nuxt-ui
Build UIs with @nuxt/ui v4 — 125+ accessible Vue components with Tailwind CSS theming. Use when creating interfaces, customizing themes to match a brand, building forms, or composing layouts like dashboards, docs sites, and chat interfaces.
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.
vue-component-testing
Applies the three-tier test taxonomy for Vue 3 applications: writes unit tests for composables and Pinia stores with Vitest, component tests for behaviour and user interactions with @testing-library/vue, and acceptance tests for full user flows with Playwright. Ensures tests focus on observable behaviour, not…
compiler-pipeline-internals
The Inkline compiler's end-to-end pipeline — parse → IR → analyze → per-target codegen → print — including the IR contracts, reactivity tracking, target rewrite rules, plugin hooks, the two compile paths, and known sharp edges. Use for any core/ work, or when reviewing it.
create-pr
Author a pull request in the Guild's standard shape — a fixed Summary / Changes / Verification / Notes skeleton that mirrors the review-gate, plus the hard anti-leak rule that no agent @mention or mention:// link ever reaches a public PR. Use whenever you are about to open a PR (e.g. /create-pr), so the PR passes…