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 OutlineDriven/outline-driven-development --skill clanggit clone --depth 1 https://github.com/OutlineDriven/outline-driven-developmentWrote 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/outlinedriven/outline-driven-development/clang)<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/clang"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/clang/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/outlinedriven/outline-driven-development/clang"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/clang.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.01671 |
| Opus 5 | $0.00026 | $0.00835 |
| Sonnet 5 | $0.00010 | $0.00334 |
| Haiku 4.5 | $0.00005 | $0.00167 |
Grade A, and why
clang 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clang
Contract
| Field | Bound contract |
|---|---|
| Trigger | A project compiles with clang or clang++ and the user asks for better diagnostics, wants to see what the optimizer did or skipped, wants static analysis with clang-tidy, needs LTO through lld or LLVM PGO, or is moving a GCC build to Clang. |
| Authority | Read-only. The skill emits flags, commands, and readings to chat; clang-tidy --fix is shown but the user runs it. Rollback is not needed because no project file is written. No remote mutation. |
| Side effect | Chat output. Scratch compiles target a scratch file, never the project tree. |
| Done | The requested flag set or command is reported, every flag in it is confirmed against the installed Clang, and every remark or diagnostic in the request has a reading and a next action. |
Inputs
- Compiler version: required, from
clang --version. The current stable line is LLVM/Clang 23.1.0; Apple'sclangreports an Apple version and lags upstream. - The task: required. One of diagnostics, remarks, static analysis, LTO, PGO, GCC migration, or macOS specifics.
- Source file or compile command that reproduces the question: required for diagnostics and remarks.
- Linker available (
ld.lld,ld64, GNUld): required for LTO questions.
Procedure
- Confirm the compiler and driver: run
clang --version. On macOS,xcrun clangresolves to the Xcode toolchain; Homebrew LLVM installs a separate upstreamclang. Done when: the vendor and version are recorded. - Map GCC flags to Clang where they differ. Clang accepts most GCC driver flags. Differences that matter:
-Ozshrinks harder than-Os;-flto=thinselects ThinLTO;-fprofile-instr-generateand-fprofile-instr-useselect LLVM's own PGO format while-fprofile-generateand-fprofile-usekeep the GCC-compatible format;-Weverythingenables every warning and suits a one-off audit, not a production build;--analyzeruns the Clang Static Analyzer where GCC has-fanalyzer. Attributes differ: gate GCC-only attributes with__has_attribute(name). Done when: each GCC flag in the request has its Clang spelling or a note that it is unchanged. - Tune diagnostics with confirmed flags:
-ferror-limit=Nstops after N errors (default 20);-fno-elide-typeprints full template types;-fdiagnostics-show-template-treeshows a tree diff for template mismatches;-ftemplate-backtrace-limit=Nbounds the instantiation backtrace;-fdiagnostics-parseable-fixitsemits fix-its in a machine-readable form;-fdiagnostics-format=viormsvcchanges the location format. Fix-it hints already print inline by default. Done when: the diagnostic flags are stated with their effect. - Read optimization remarks. Emit them with
-Rpass=<regex>(transform happened),-Rpass-missed=<regex>(transform skipped),-Rpass-analysis=<regex>(why), for exampleclang -O2 -Rpass-analysis=loop-vectorize src.c. Save all remarks with-fsave-optimization-record, which writes<object>.opt.yamlnext to the object file. Interpret: an inline remark on a hot path is good;loop not vectorized: loop control flow is not understoodcalls for restructuring the loop; a reordering-safety remark calls for__restrict__or#pragma clang loop vectorize(assume_safety)after the user proves no aliasing. Done when: each remark in the request has a reading and a next action. - Run static analysis. Built-in analyzer:
clang --analyze -Xanalyzer -analyzer-output=text src.c. clang-tidy:clang-tidy src.cpp -- -std=c++20 -I<dir>for one file,-p build/againstcompile_commands.json(generate it withcmake -DCMAKE_EXPORT_COMPILE_COMMANDS=ON),run-clang-tidy -j<N> -p build/for the tree,-checks='clang-analyzer-*,bugprone-*,modernize-*,performance-*'to select families,--fixto apply fix-its in place. Suppress one line with// NOLINT(check-name)or the following line with// NOLINTNEXTLINE(check-name). Done when: the analysis command and check families match the code class. - Configure LTO. Full:
clang -O2 -flto -fuse-ld=lld. Thin:clang -O2 -flto=thin -fuse-ld=lld. Confirm the linker withclang -fuse-ld=lld -Wl,--version. ThinLTO links faster than full LTO on large programs; measure the code-quality difference on the project rather than assuming a ratio.-fwhole-program-vtablesand-fvirtual-function-eliminationneed LTO. On macOS the default linker isld64;-fuse-ld=lldneeds an upstream LLVM install. Done when: the LTO mode, linker, and confirmation command are stated. - Configure PGO:
clang -O2 -fprofile-instr-generateto instrument, run the workload (writesdefault.profraw; setLLVM_PROFILE_FILE="prog-%p.profraw"for parallel runs),llvm-profdata merge -output=prog.profdata *.profraw, thenclang -O2 -fprofile-instr-use=prog.profdata. Sampling-based profiles use-fprofile-sample-use=<file>. The full flow, context-sensitive PGO, and BOLT: use pgo. Done when: the four PGO commands are listed. - Handle macOS specifics when asked: set the deployment target with
-mmacosx-version-min=X.Y; sanitizer runtimes are injected at load, so do not strip a sanitized binary;xcrun clangselects the Xcode toolchain. Done when: the macOS points relevant to the request are stated. - Confirm every flag against the installed Clang with a scratch compile; drop any the driver rejects and say so. Done when: no unconfirmed flag remains.
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.
- 3d ago First seen · 49 lines · 51 tokens per session scan A 0ef0f9c98ab1
clang is a skill published in the GitHub repository OutlineDriven/outline-driven-development (52 stars, last pushed 3d ago), licensed Apache-2.0. It adds 51 tokens to every session and 1,671 once invoked, about $0.0003 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-06.
Other skills, from other repositories
cpp-pro
Writes, optimizes, and debugs C++ applications using modern C++20/23 features, template metaprogramming, and high-performance systems techniques. Use when building or refactoring C++ code requiring concepts, ranges, coroutines, SIMD optimization, or careful memory management — or when addressing performance…
memory-safety-patterns
Implement memory-safe programming with RAII, ownership, smart pointers, and resource management across Rust, C++, and C. Use when writing safe systems code, managing resources, or preventing memory bugs.
cpp
Comprehensive C/C++ programming reference covering everything from C11-C23 and C++11-C++23, system programming, CUDA GPU computing, debugging tools, Rust interop, and advanced topics. Use for: C/C++ questions, C/C++ interview preparation, modern language features, RAII/memory management, templates/generics, CUDA…
cpp-debugging
Use when a C++ failure involves memory lifetime, undefined behavior, native crashes, or debugger-only state — debug with symbols, sanitizers, and platform-native debuggers before patching symptoms.
memory-safety-patterns
Implement memory-safe programming with RAII, ownership, smart pointers, and resource management across Rust, C++, and C. Use when writing safe systems code, managing resources, or preventing memory bugs.
gcc
GCC compiler skill for C/C++ projects. Use when selecting optimization levels, warning flags, debug builds, LTO, sanitizer instrumentation, or diagnosing compilation errors with GCC. Covers flag selection for debug vs release, ABI concerns, preprocessor macros, profile-guided optimization, and integration with build…