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/szaghi/dotfiles/openacc-3.4npx skills add szaghi/dotfiles --skill openacc-3.4git clone --depth 1 https://github.com/szaghi/dotfilesWrote 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/szaghi/dotfiles/openacc-3.4)<a href="https://agentmods.dev/skills/szaghi/dotfiles/openacc-3.4"><img src="https://agentmods.dev/badge/skills/szaghi/dotfiles/openacc-3.4.svg" alt="Measured on agentmods" height="20"></a>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.00227 | $0.02552 |
| Opus 5 | $0.00113 | $0.01276 |
| Sonnet 5 | $0.00045 | $0.00510 |
| Haiku 4.5 | $0.00023 | $0.00255 |
Grade A, and why
openacc-3.4 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 6d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
15 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.
- chapters/ch01-introduction.md 4.6 KB
- chapters/ch02-directive-basics.md 4.1 KB
- chapters/ch03-compute-constructs.md 5.1 KB
- chapters/ch04-data-environment-clauses.md 5.8 KB
- chapters/ch05-loop-host-cache-combined.md 5.3 KB
- chapters/ch06-atomic-declare-executable.md 4.5 KB
- chapters/ch07-procedures-async-fortran.md 5.6 KB
- chapters/ch08-runtime-library.md 4.8 KB
- chapters/ch09-environment-variables.md 2.8 KB
- chapters/ch10-profiling-interface.md 4.2 KB
- chapters/ch11-glossary.md 4.1 KB
- cheatsheet.md 4.1 KB
- glossary.md 5.2 KB
- NOTICE 1.0 KB
- patterns.md 3.6 KB
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.
- 6d ago First seen · 126 lines · 227 tokens per session scan A 644c0f33efbd
openacc-3.4 is a skill published in the GitHub repository szaghi/dotfiles (5 stars, last pushed 6d ago), with no licence file. It adds 227 tokens to every session and 2,552 once invoked, about $0.0011 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-31.
Other skills, from other repositories
cuopt-numerical-optimization-api
LP, MILP, and QP (beta) with cuOpt — Python, C, and CLI. Use when the user is solving LP, MILP, or QP with any cuOpt interface.
cuopt-developer
Modify, build, test, debug, and contribute to NVIDIA cuOpt (C++/CUDA, Python, server, CI). Use for solver internals, PRs, DCO, and code conventions.
huawei-cloud-ascendc-operator-performance-optim
Develop and optimize custom operators using AscendC programming language. Analyze operator performance bottlenecks and conduct optimization validation. Based on AscendC and CANN toolkit Use this skill when the user wants to: (1) optimize performance-critical operators on Ascend NPU, (2) develop custom operators for…
cuda-c-basics
CUDA C 核心概念、内核结构和标准编程模式.
torchtalk-analyzer
Analyze PyTorch internals across Python, C++, and CUDA layers using the TorchTalk MCP server. Use when asked about how PyTorch operators work internally, where functions are implemented, what would break if code is modified, or finding tests for PyTorch operators.
torchtalk-trace
Trace a PyTorch function's cross-language binding chain (Python -> C++ -> CUDA).