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 xmake-io/xmake-skills --skill xmake-fortrangit clone --depth 1 https://github.com/xmake-io/xmake-skillsWrote 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/xmake-io/xmake-skills/xmake-fortran)<a href="https://agentmods.dev/skills/xmake-io/xmake-skills/xmake-fortran"><img src="https://agentmods.dev/badge/skills/xmake-io/xmake-skills/xmake-fortran/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/xmake-io/xmake-skills/xmake-fortran"><img src="https://agentmods.dev/badge/skills/xmake-io/xmake-skills/xmake-fortran.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.00056 | $0.00794 |
| Opus 5 | $0.00028 | $0.00397 |
| Sonnet 5 | $0.00011 | $0.00159 |
| Haiku 4.5 | $0.00006 | $0.00079 |
Grade A, and why
xmake-fortran 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 11d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Building Fortran with Xmake
Xmake supports Fortran since v2.3.6 via gfortran, and Intel Fortran (ifort) since v2.3.8.
1. Minimal project
xmake create -l fortran -t console hello
cd hello
xmake run
add_rules("mode.debug", "mode.release")
target("hello")
set_kind("binary")
add_files("src/*.f90")
Recognized extensions: .f, .F, .f90, .F90, .f95, .F95, .f03, .F03, .f08, .F08, .for, .FOR. The uppercase variants get preprocessed.
2. Target kinds
target("app") set_kind("binary")
target("mylib") set_kind("static")
target("mydyn") set_kind("shared")
3. Compiler selection
xmake f --toolchain=gfortran # default gfortran
xmake f --toolchain=ifort # Intel Fortran
xmake f --toolchain=ifx # Intel oneAPI LLVM-based Fortran
Pin a specific install with --sdk=/opt/intel/oneapi.
4. Flags
target("app")
add_files("src/*.f90")
add_fcflags("-O3", "-ffree-form") -- gfortran flags
add_ldflags("-lm")
add_fcflags = Fortran compiler flags.
5. Mixing Fortran with C
target("solver")
set_kind("static")
add_files("src/*.f90", "src/*.c")
add_includedirs("include", {public = true})
target("app")
set_kind("binary")
add_files("src/main.cpp")
add_deps("solver")
set_languages("c++17")
Use iso_c_binding on the Fortran side and extern "C" on the C++ side. Xmake handles the link step — gfortran's runtime is added automatically when Fortran objects are present.
6. Modules (Fortran modules, not C++ modules)
Fortran module/end module produces .mod files. Xmake tracks them automatically for dependency ordering — list source files in add_files in any order; xmake scans USE statements.
Pitfalls
- Fixed-form vs free-form.
.f/.fordefault to fixed form (columns matter);.f90+ default to free form. Flag overrides work per-file if needed. .modleaking across targets. Each target has its own module cache. Share modules by linking the static/shared library and letting xmake propagate the-Ipath.- Intel compiler flag dialect.
ifortandifxdiffer fromgfortranin many flag names. Gate withis_toolchain. - Mixing Fortran and C++ without a C intermediate. Fortran↔C++ name mangling is messy; always bridge through a C layer.
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.
- 11d ago First seen · 90 lines · 56 tokens per session scan A 5ca26cfdc702
xmake-fortran is a skill published in the GitHub repository xmake-io/xmake-skills (24 stars, last pushed 18d ago), licensed Apache-2.0. It adds 56 tokens to every session and 794 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
jupyter-notebook
Iterative Python via live Jupyter kernel (hamelnb).
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
pennylane
Hardware-agnostic quantum ML framework with automatic differentiation. Use when training quantum circuits via gradients, building hybrid quantum-classical models, or needing device portability across IBM/Google/Rigetti/IonQ. Best for variational algorithms (VQE, QAOA), quantum neural networks, and integration with…
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.
rocm-kernels
Provides guidance for writing and benchmarking optimized Triton kernels for AMD GPUs (MI355X, R9700) on ROCm, targeting HuggingFace diffusers (LTX-Video, SD3, FLUX) and transformers. Core kernels: RMSNorm, RoPE 3D, GEGLU, AdaLN. Includes XCD swizzle, autotune, diffusers integration patterns, and LTX-Video pipeline…
cudaq-importing
Use when porting circuits from another framework (e.g. Qiskit) into CUDA-Q kernels while preserving the source algorithm and validation fidelity.