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/authoring-projectsnpx skills add NVIDIA/elements --skill authoring-projectsgit 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.00097 | $0.00839 |
| Opus 5 | $0.00048 | $0.00419 |
| Sonnet 5 | $0.00019 | $0.00168 |
| Haiku 4.5 | $0.00010 | $0.00084 |
Grade A, and why
authoring-projects 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoring Projects
Create a private-by-default project from a current in-repository reference, then wire every consumer before customizing the component.
Required context
- Read the repository
AGENTS.md. - Read references/integration-checklist.md.
- Use the
authoring-componentsskill for the component class, API, examples, and five test files. - Use the
guidance-build-systemskill for Wireit changes and theauthoring-testingskill when modifying tests. - Read
projects/internals/RELEASE.mdonly when the user wants the package published.
Workflow
-
Confirm the kebab-case project/component name, purpose, package description, and whether the project is private or publish-ready. Default the component name to the project name and keep a new scaffold private.
-
Inspect
git status, confirmprojects/<name>does not exist, and preserve unrelated work. -
Preview the deterministic scaffold from the repository root:
node .agents/skills/authoring-projects/scripts/scaffold-project.mjs \ --name <component-name> \ --description "<package and component description>" \ --dry-run -
Review the planned paths, then rerun without
--dry-run. Pass--reference <project-name>when another standalone project is a better structural match. -
Customize the placeholder component through the
authoring-componentsworkflow. Keepindex.tsside-effect free, isolate registration indefine.ts, use@since 0.0.0, and make the@documentationURL match the generated site route. -
Refresh generated workspace state:
mise exec -- pnpm install mise exec -- pnpm run format:fix mise exec -- pnpm run notice -
Run the project checks listed in its
DEVELOPMENT.md, then verify the repository integrations:mise exec -- pnpm -C projects/<component-name> run ci mise exec -- pnpm -C projects/<component-name> run test:lighthouse mise exec -- pnpm -C projects/internals/metadata run generate:api mise exec -- pnpm -C projects/internals/metadata run build mise exec -- pnpm -C projects/site run build mise exec -- pnpm run lint:knip
What ships with it
2 files 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 · 68 lines · 97 tokens per session scan A 4aa51c59dd7e
authoring-projects is a skill published in the GitHub repository NVIDIA/elements (83 stars, last pushed 2d ago), licensed Apache-2.0. It adds 97 tokens to every session and 839 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
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.