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/nvcf/documentation-stylenpx skills add NVIDIA/nvcf --skill documentation-stylegit clone --depth 1 https://github.com/NVIDIA/nvcfWhat 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.00061 | $0.01147 |
| Opus 5 | $0.00030 | $0.00574 |
| Sonnet 5 | $0.00012 | $0.00229 |
| Haiku 4.5 | $0.00006 | $0.00115 |
Grade A, and why
documentation-style 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation and writing style
Purpose
Keep NVCF documentation plain, consistent, and useful for external readers. Write short docs an agent or contributor can act on without private context. Avoid typographic Unicode that breaks grep and diff tools, and avoid emphasis patterns that make docs noisy.
When to use
- Any new or edited public Markdown in this repo.
AGENTS.md,CLAUDE.md,SKILL.md, READMEs, plans, and guides.- GitHub issue bodies, commit messages, and Pull Request descriptions.
- Existing docs you are changing for another reason.
Instructions
-
No markdown bold for emphasis. Do not use
**...**,__...__, raw HTML<b>, or<strong>. Use headings, lists, andbackticksfor paths, commands, env vars, and identifiers. -
No emojis in documentation or user-facing prose.
-
No em-dash (Unicode U+2014) or en-dash (U+2013). Split the thought into two sentences, or use a comma, semicolon, parenthesis, or colon.
-
ASCII only in committed prose. Avoid smart quotes, ellipsis characters, non-breaking spaces, arrows, and other typographic Unicode. Prefer
->over an arrow glyph and...over a single-character ellipsis. Code blocks and quoted fixtures are exempt. -
Be succinct. Prefer short sentences and direct wording. Cut filler and repetition. Keep one idea per sentence when possible.
-
Prefer lists for short, scan-friendly structure. Use bullets for unordered items and numbered lists when sequence, priority, or stable rule references matter. Use tables only when columns make comparison, status, option tradeoffs, or matrix decisions easier. Do not turn a short list into a table.
-
Be easy to understand. Define acronyms on first use if the audience is broad. Prefer concrete examples over abstract jargon.
-
Write for GitHub readers. Use public names, public paths, and public behavior. Replace private evidence with the user-visible reason for the change.
-
Keep agent guidance actionable. Say when to use a skill, what to inspect first, what command to run, and what done means. Do not add temporary branch status, Pull Request queues, merge-order notes, or private routing details.
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 · 146 lines · 61 tokens per session scan A ab14d8486219
documentation-style is a skill published in the GitHub repository NVIDIA/nvcf (202 stars, last pushed 2d ago), licensed Apache-2.0. It adds 61 tokens to every session and 1,147 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-08-30.
Other skills, from other repositories
eli5
Transform technical jargon into clear explanations using before/after comparisons, metaphors, and practical context.
pr
Creates and updates GitHub pull requests for cloudflare-docs changes. Load when asked to open, create, submit, update, or edit a PR, or write a PR title or description. Covers title conventions, branch naming, PR body structure, and the documentation checklist template.
workers-code-review
Reviews Workers and Cloudflare Developer Platform code for type correctness, API usage, and configuration validity. Load when reviewing TypeScript/JavaScript using Workers APIs, wrangler.jsonc/toml config, or Cloudflare bindings (KV, R2, D1, Durable Objects, Queues, Vectorize, AI, Hyperdrive).
reconcile-code-review
Reconcile raw specialist findings against the previous bot review and human PR comments to produce a final classified finding list.
contributing
Use when contributing to the Cloudflare Docs repository — writing or editing documentation pages, choosing content types or components, adding changelog entries, reviewing docs, or learning how to contribute.
dependabot-review
Analyzes a Dependabot PR to determine what actually changed in each bumped package and whether those changes affect this repo. Reports changed APIs/methods, which doc pages use them, and the realistic probability of any visible impact on the docs site.