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 arm/mcp --skill arm-enablementgit clone --depth 1 https://github.com/arm/mcpWrote 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/arm/mcp/arm-enablement)<a href="https://agentmods.dev/skills/arm/mcp/arm-enablement"><img src="https://agentmods.dev/badge/skills/arm/mcp/arm-enablement/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/arm/mcp/arm-enablement"><img src="https://agentmods.dev/badge/skills/arm/mcp/arm-enablement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 102 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00079 | $0.02256 |
| Opus 5.5 | $0.00032 | $0.00902 |
| Sonnet 5.5 | $0.00016 | $0.00451 |
| Haiku 4.5 | $0.00008 | $0.00226 |
Grade A, and why
arm-enablement 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 1mo 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arm Enablement
Evaluate an OSS repository for end-to-end Arm readiness and create:
arm-enablement-report.mdat the target repository root.arm-enablement-report.pdfexported from that Markdown source.
Write for OSS maintainers, developer-relations teams, and CNCF-style community audiences. Tell a concise case-study story while keeping every technical claim auditable.
Establish Scope
- Treat the current repository as the target unless the user supplies a GitHub URL.
- If a URL is supplied, clone it into an empty workspace or an
arm-enablement-target/subdirectory. - Prefer scanning the local target mounted at MCP
/workspace. Use the scanner'sgit_repoinput only for an initial report-only scan when the current workspace is unrelated to the target and there are no local or uncommitted changes to assess. Never usegit_repoto validate fixes; mount the changed checkout at/workspaceand omitgit_repo. - Default to report-only mode. Create only the two report files unless the user explicitly asks to apply fixes.
- If fixes are requested, make the smallest necessary source changes, update the report, and rerun affected checks. Do not commit unless the user asks.
- Record the repository URL, current commit, assessment mode, host architecture, and date.
Verify Arm MCP
Before assessing the project:
- Confirm that the configured
arm-mcpserver exposesmigrate_ease_scan,knowledge_base_search,check_image,skopeo, andmcaas applicable. - Treat these as MCP tools, not command-line programs. Do not search for similarly named executables on
PATH. - Confirm that the target checkout visible to Codex is the same checkout mounted at
/workspacein the Arm MCP container. Compare a distinctive file or the repository root listing. - If the server or workspace mapping is unavailable, stop and report the exact configuration problem. Point to the Arm MCP installation guide; do not fabricate scan results.
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.
- 1mo ago Changed 743087980c78
- 1mo ago First seen · 107 lines · 79 tokens per session scan A 541812e81f8c
arm-enablement is a skill published in the GitHub repository arm/mcp (95 stars, last pushed today), licensed Apache-2.0. It adds 79 tokens to every session and 2,256 once invoked, about $0.0003 per session on Opus 5.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
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
holoscan-install-wheel
Install Holoscan SDK 5.x CUDA 13 Python wheels in an isolated environment, choosing the full stack or version-matched components.
offensive-z-wave
Z-Wave attack methodology — sniffing with Z-Force / EZ-Wave / RTL-SDR + ZniffMobile, S0 (legacy) network-key derivation flaw and key reuse, S2 (modern) ECDH commissioning analysis, replay/injection on unauthenticated nodes, default-key brute-force on test deployments, and home-automation hub pivots. Use when targeting…
doca-socket-relay
Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…
hsb-flash
Flash the FPGA on an HSB board connected to an NVIDIA devkit. Supports HSB Lattice boards (FPGA versions 2407, 2412, 2507, 2510) and Leopard Imaging VB1940 "all-in-one" cameras (FPGA versions 2507, 2510). Uses release-specific YAML manifests and board-type-specific program commands. Lattice and VB1940 commands must…