local-model-selection

Recommends local LLM models, quants, and configurations for Hermes Agent by VRAM tier.

115|9|Updated Aug 5, 2026
One-click install
npx skills add https://github.com/AtlasOmnia/donna-starter --skill local-model-selection-atlasomnia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: local-model-selection
Source: https://github.com/AtlasOmnia/donna-starter/tree/main/skills/autonomous-ai-agents/local-model-selection
Command: npx skills add https://github.com/AtlasOmnia/donna-starter --skill local-model-selection-atlasomnia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Choosing the right local LLM for Hermes Agent is confusing: model families have inconsistent size tiers, quant formats trade quality for VRAM, and uncensored variants vary widely in reliability. This Skill provides verified, hardware-specific recommendations so you avoid downloading models that do not exist, do not fit, or fail in agent tool-calling loops. ## Core Features & Use Cases - VRAM-tier recommendations: Concrete model and quant picks for 8-12GB, 16GB, 24GB, and 32GB GPUs, plus Apple Silicon memory tiers, with exact HuggingFace repositories and GGUF filenames. - Quant and KV cache guidance: Explains when Q4_K_M is acceptable versus when Q6_K is the floor for agent work, and how to configure KV cache precision to avoid system-RAM spill. - Dual-GPU and auxiliary model setup: Covers LM Studio multi-model serving, llama.cpp strict GPU isolation, and cross-family auxiliary model selection for compression, approval, and vision tasks. - Use Case: A user with a 16GB GPU asks which uncensored model to run as a Hermes auxiliary. The Skill recommends Gemma 4 26B-A4B Heretic at Q4_K_M with the exact repository, explains why cross-family pairing reduces correlated failures, and provides verification steps via LM Studio's API endpoints. ## Quick Start Ask which local model and quant you should run for Hermes Agent on your specific GPU and VRAM amount.

Frequently Asked Questions about local-model-selection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What local LLM should I run on 16GB VRAM for Hermes Agent?

Gemma 4 26B-A4B Heretic at Q4_K_M (~14GB) is the top 16GB pick, offering MoE speed, vision, and tool calling. Alternatives include Mistral Small 24B abliterated for dense quality and GPT-OSS 20B Heretic for the highest benchmark scores.

Which GGUF quant should I use for agent tool-calling workloads?

Q6_K is the preferred minimum for serious agent work with 27B-class dense models, and Q5_K_M is the practical floor. Q4_K_M amplifies errors in long sequential tool-call chains, though MoE models tolerate lower quants better.

Dense vs MoE model for a primary Hermes agent brain?

Dense models consistently outperform same-family MoE models on agentic benchmarks like Terminal-Bench and SkillsBench, despite being slower. Choose MoE only when throughput matters more than quality, such as RAG pipelines or concurrent serving.

Can LM Studio pin one model to each GPU in a dual-GPU setup?

No. LM Studio auto-balances across GPUs and its GPU priority setting only affects allocation order, not hard isolation. For strict per-GPU pinning, run separate runtimes such as llama-server with CUDA_VISIBLE_DEVICES set per instance.

Why does my local model fail Hermes tool calls with a grammar parse error?

A 'failed to parse grammar' error before generation usually means llama.cpp rejected an oversized nested schema constraint, not a bad checkpoint. Compare slim-tool versus full-tool requests and fix the offending schema rather than changing quants.

How do I choose an auxiliary model for Hermes context compression?

The compressor's live context should meet or exceed the main model's compression trigger, since Hermes sends the whole compressible middle in one request. Prefer stock instruct checkpoints at Q6 or better with one parallel slot, such as Qwen3.6-27B at native 262K context.