A guide for running GGUF-format language models locally with llama.cpp, including choosing model files for available computer memory or graphics memory.

Discover llama.cpp models on Hugging Face, compare compressed model versions, and build commands for running them on CPUs or supported GPUs.

It helps you find a compatible model file and the right command without guessing among many model versions.

llama-cpp — Skill by jscholz

Install

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.

agentmods

npx agentmods add skills/jscholz/hermes-agent-workflow/llama-cpp

Any agent

npx skills add jscholz/hermes-agent-workflow --skill llama-cpp

Clone the repo

git clone --depth 1 https://github.com/jscholz/hermes-agent-workflow

Made for: Claude Code, Codex.

Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,501 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. Scan, not verified.

Origin 98% copy Near-identical to another mod in the catalogue.

Token cost

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	$0.00018	$0.02501
Opus 5	$0.00009	$0.01251
Sonnet 5	$0.00004	$0.00500
Haiku 4.5	$0.00002	$0.00250

Measured 2d ago against content hash 06b21e4aadcf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

llama-cpp scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl http://localhost:8080/v1/chat/completions \

Origin

This is a copy

98% identical to llama-cpp — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/mlops/inference/llama-cpp/SKILL.md · 249 lines

How it starts

The opening of the file, as written. The whole thing — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.

llama.cpp + GGUF

Use this skill for local GGUF inference, quant selection, or Hugging Face repo discovery for llama.cpp.

When to use

Run local models on CPU, Apple Silicon, CUDA, ROCm, or Intel GPUs
Find the right GGUF for a specific Hugging Face repo
Build a llama-server or llama-cli command from the Hub
Search the Hub for models that already support llama.cpp
Enumerate available .gguf files and sizes for a repo
Decide between Q4/Q5/Q6/IQ variants for the user's RAM or VRAM

Model Discovery workflow

Prefer URL workflows before asking for hf, Python, or custom scripts.

Search for candidate repos on the Hub:
- Base: https://huggingface.co/models?apps=llama.cpp&sort=trending
- Add search=<term> for a model family
- Add num_parameters=min:0,max:24B or similar when the user has size constraints
Open the repo with the llama.cpp local-app view:
- https://huggingface.co/<repo>?local-app=llama.cpp
Treat the local-app snippet as the source of truth when it is visible:
- copy the exact llama-server or llama-cli command
- report the recommended quant exactly as HF shows it
Read the same ?local-app=llama.cpp URL as page text or HTML and extract the section under Hardware compatibility:
- prefer its exact quant labels and sizes over generic tables
- keep repo-specific labels such as UD-Q4_K_M or IQ4_NL_XL
- if that section is not visible in the fetched page source, say so and fall back to the tree API plus generic quant guidance
Query the tree API to confirm what actually exists:
- https://huggingface.co/api/models/<repo>/tree/main?recursive=true
- keep entries where type is file and path ends with .gguf
- use path and size as the source of truth for filenames and byte sizes
- separate quantized checkpoints from mmproj-*.gguf projector files and BF16/ shard files
- use https://huggingface.co/<repo>/tree/main only as a human fallback
If the local-app snippet is not text-visible, reconstruct the command from the repo plus the chosen quant:
- shorthand quant selection: llama-server -hf <repo>:<QUANT>
- exact-file fallback: llama-server --hf-repo <repo> --hf-file <filename.gguf>
Only suggest conversion from Transformers weights if the repo does not already expose GGUF files.

Read the full file on GitHub · 249 lines

Files

What ships with it

6 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.

Changes

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 · 249 lines · 18 tokens per session scan A 06b21e4aadcf

Subscribe to this mod's changes

llama-cpp is a skill published in the GitHub repository jscholz/hermes-agent-workflow (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 2,501 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 98% identical to llama-cpp, differing in 3 lines, and is treated as a copy.

Data and AI

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

llama-cpp