elements: Hook for Claude Code

.claude/settings.json

PostToolUse is a hook for Claude Code from NVIDIA/elements. Its token cost is not measured, scanned A, original, Apache-2.0.

An automatic action that runs after the agent edits or writes a file. It starts a project script named post-tool-use-edit-write.sh.

In plain words
What is it for?
Use it to run the repository’s formatter and code-quality checks after file edits.
Why use it?
It keeps formatting and lint checks from being skipped after code changes. Problems can be detected immediately after an edit or new file is written.

Hook for Claude Code ✓ vendor

Written for Claude Code: ${CLAUDE_PROJECT_DIR variable.

This is NVIDIA/elements's own configuration. It tells Claude Code how to work on elements itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything elements configures →

One of 6 entries in settings.json upstream. Installing this one merges just its entry into your config; the other 5 are separate, each on its own page.

About the project

NVIDIA Elements is a design system and agent-oriented toolkit for building operational interfaces for AI/ML, robotics, and autonomous-vehicle software. Its CLI and MCP tools provide component APIs, design tokens, examples, imports, validation, and setup guidance across several web frameworks.

NVIDIA/elements · 102 stars · on GitHub · nvidia.github.io

Reuse

Borrowing it

Nothing to install: this file belongs to NVIDIA/elements. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/NVIDIA/elements/main/.claude/settings.json
Clone the repo
git clone --depth 1 https://github.com/NVIDIA/elements

Made for: Claude Code.

Wrote 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.

agentmods badge for PostToolUse

README.md
[![agentmods](https://agentmods.dev/badge/hooks/nvidia/elements/post-tool-use/github.svg)](https://agentmods.dev/hooks/nvidia/elements/post-tool-use)
Your own site
<a href="https://agentmods.dev/hooks/nvidia/elements/post-tool-use"><img src="https://agentmods.dev/badge/hooks/nvidia/elements/post-tool-use/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.

agentmods 80×15 button for PostToolUse

Your own site · 80×15
<a href="https://agentmods.dev/hooks/nvidia/elements/post-tool-use"><img src="https://agentmods.dev/badge/hooks/nvidia/elements/post-tool-use.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

PostToolUse 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 1mo ago.

A static scan of the commands this hook runs, not an audit. A hook is shell that executes on your machine at the event it names, which is why every command in it is printed with what was found.

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.

.claude/settings.json · 14 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "Edit|Write",
      "hooks": [
        {
          "type": "command",
          "command": "\"${AGENTS_PROJECT_DIR:-${CLAUDE_PROJECT_DIR:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)}}\"/.agents/hooks/post-tool-use-edit-write.sh",
          "statusMessage": "Running formatter and linters..."
        }
      ]
    }
  ]
}
Same file

What else settings.json configures

This page is one entry in a file that holds 6. Installing the file brings all of them; each is measured and scanned on its own page.

Changes

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.

  1. 1mo ago First seen · 14 lines scan A 2fcf9030e8c8

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository NVIDIA/elements (102 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: a hook is shell that never enters the context. 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.