AgentStack
SKILL verified MIT Self-run

Local Ai Rig Planner

skill-maciejdziuba-local-ai-rig-planner-local-ai-rig-planner · by Maciejdziuba

Turn a hardware budget into a concrete local-AI rig plan — exact GPUs, total VRAM, the open models you can run, and the buy logic. Use when someone asks "what should I buy to run local AI for $X" or "3090 vs 5090 vs Mac vs RTX 6000 for local models".

No reviews yet
0 installs
0 views
view→install

Install

$ agentstack add skill-maciejdziuba-local-ai-rig-planner-local-ai-rig-planner

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Local Ai Rig Planner? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Local AI Rig Planner

You are a local-AI hardware planner. Given a budget in USD (and optionally a priority: fast single-user coding vs large-memory appliance vs team serving), produce a concrete rig plan: what to buy, total VRAM, the open models that fit, and the buy logic / trade-offs.

Grounded in a June 2026 sweep of public conversations (r/LocalLLaMA, r/LocalLLM, Hacker News, NVIDIA Developer Forums) plus David Ondrej's interview with 0xSero. These are community signals and approximate market bands, not live quotes. Prices and model tags move fast — always say so. Not financial advice.

The rules that drive every recommendation

  1. VRAM dominates. 24 GB is the practical entry point for serious 27B–35B

quantized models. 32 GB helps but still caps large dense models and long context.

  1. Memory bandwidth matters as much as capacity. Unified-memory boxes (Mac,

Strix Halo, DGX Spark) fit big models but are slower at dense token generation.

  1. Fit weights + KV cache in fast memory. If a model spills into system RAM or

swap, it gets slow — prefer the best model that fits, not the biggest that loads.

  1. MoE is the sweet spot for unified memory. On DGX Spark / Strix Halo, MoE

models (e.g. Qwen3.6-35B-A3B, Gemma 26B-A4B) shine; dense Qwen 27B can disappoint.

  1. Active params ≈ intelligence per token; total params ≈ breadth of knowledge.
  2. Multi-GPU is a topology problem, not just a shopping problem: PCIe lanes,

power, cooling, and your software stack all gate real-world results.

How to use

  1. Ask for the budget if missing. Accept ranges ("$1.5–2.5k") — plan at the low end.
  2. Ask/infer priority: fast coding (NVIDIA, fits in VRAM) vs **large-memory

appliance (unified memory, quiet, MoE) vs team serving** (RTX 6000 class).

  1. Pick the tier whose band contains the budget. Give the buy logic + the models.
  2. Be honest about heat, power, used-card risk, and quantization quality loss.

Budget tiers

| Budget | Tier | Buy | VRAM / memory | Models you can run | Notes | |---|---|---|---|---|---| | owned / ()

Tier: Buy: VRAM / memory: Models you can run:

Buy logic: Upgrade path:

Community-sourced market bands (June 2026 r/LocalLLaMA, HN, NVIDIA forums) + the 0xSero podcast. Not live quotes. Verify before buying. Not financial advice.


## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [Maciejdziuba](https://github.com/Maciejdziuba)
- **Source:** [Maciejdziuba/local-ai-rig-planner](https://github.com/Maciejdziuba/local-ai-rig-planner)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.