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/cuda-quantum/cudaq-guidenpx skills add NVIDIA/cuda-quantum --skill cudaq-guidegit clone --depth 1 https://github.com/NVIDIA/cuda-quantumWhat 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.00026 | $0.01215 |
| Opus 5 | $0.00013 | $0.00607 |
| Sonnet 5 | $0.00005 | $0.00243 |
| Haiku 4.5 | $0.00003 | $0.00121 |
Grade A, and why
cudaq-guide 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CUDA-Q Guide
Purpose
Guide users through CUDA-Q installation, basic kernels, GPU simulation targets,
QPU access, built-in applications, multi-GPU execution, and Python
@cudaq.kernel authoring. For Qiskit-to-CUDA-Q ports, route to the
qiskit-to-cudaq skill instead.
Prerequisites
- Python 3.10+ for Python CUDA-Q workflows.
- CUDA Toolkit and an NVIDIA GPU for GPU-accelerated targets on Linux.
- CPU-only simulation is available through
qpp-cpu; macOS is CPU-only. - C++ workflows require Linux or WSL and C++20.
- QPU workflows require provider-specific credentials and accounts.
Instructions
- Invoke with
/cudaq-guide [argument]. - If no argument is given, display the onboarding menu and ask which topic the user wants.
- Use the routing table below to choose the relevant reference file.
- Read local CUDA-Q documentation files when the answer depends on a specific CUDA-Q version or backend behavior.
- Do not answer Qiskit porting questions from this skill; use
qiskit-to-cudaq.
Routing by Argument
| Argument | Action | Reference |
|---|---|---|
install |
Walk through Python or C++ installation and validation. | references/onboarding.md |
test-program |
Build and run a Bell-state kernel. | references/onboarding.md |
gpu-sim |
Select GPU, multi-GPU, tensor-network, or CPU targets. | references/onboarding.md |
qpu |
Guide provider selection and credential-safe QPU setup. | references/onboarding.md |
applications |
Summarize CUDA-Q application areas and notebooks. | references/onboarding.md |
parallelize |
Choose mgpu, mqpu, async dispatch, or distributed observe. |
references/onboarding.md |
author |
Author CUDA-Q Python kernels, select execution APIs, and debug compiler issues. | references/authoring.md |
| (none) | Print the menu below and ask which topic to explore. | This file |
What ships with it
8 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.
- 3d ago First seen · 117 lines · 26 tokens per session scan A 0ae9429f906b
cudaq-guide is a skill published in the GitHub repository NVIDIA/cuda-quantum (1,122 stars, last pushed 3d ago), licensed Apache-2.0. It adds 26 tokens to every session and 1,215 once invoked, about $0.0001 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
cudaq-guide
CUDA-Q onboarding guide for installation, test programs, GPU simulation, QPU hardware, and quantum applications.
cudaq-guide
CUDA-Q onboarding guide for installation, test programs, GPU simulation, QPU hardware, and quantum applications.
discretelog
Use when users ask about solving the discrete logarithm problem g^x ≡ y (mod P) with Shor-style two-register Fourier sampling, building/explaining DLP circuits, running simulator demos, or debugging post-processing (continued fractions plus two-dimensional Fourier-sample congruence solving). Triggers: discrete log…
shor
Use this skill when the user asks for Shor integer factorization, quantum order-finding, period estimation, or implementing/running/debugging ShorAlgorithm in this repository (especially matrix/operator methods, IQFT-based phase post-processing, and continued-fraction period recovery). Keywords: shor, factor N, order…
linear-combination
Analytic quantum gradient and Quantum Geometric Tensor (QGT) estimation via linear combination of unitaries (LCU). Supports Estimator (expectation value gradients), Sampler (probability distribution gradients), and QGT primitives with configurable derivative types. Skill-first for covered code generation, runnable…
aqc
Explains and demonstrates UnitaryLab's small-scale adiabatic quantum linear-system solver. Use it for AQC or QLSP questions, simulator examples, and work involving Householder state preparation, SVD block encoding, adiabatic schedules, post-selection, solution rescaling, or residual checks.