Skip to content
Back to skills

Ollama Hub

CSecurity

Manage, benchmark, and switch between local Ollama models with

  • 14 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 7, 2026
ai-agentsbashapiperformance

Works with

  • api

Security analysis

C71/100
  • mediumUses curl or wget to download content
  • criticalModifies startup scripts or system services for persistence

Pro scans all 2 files and shows the line behind each finding

Scanned September 7, 2026

npx -y skills add modbender/skill-library-mcp --skill ollama-hub --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ollama Hub?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ollama Hub
[![Security: C β€” Skills Directory](https://www.skillsdirectory.com/api/skills/modbender-ollama-hub/badge)](https://www.skillsdirectory.com/skills/modbender-ollama-hub)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ollama-hub
description: Manage, benchmark, and switch between local Ollama models with
  performance comparison.
---


# Ollama Hub

Manage and benchmark local Ollama models.

**Use when** listing models, pulling new ones, benchmarking performance, or comparing models.

## Requirements

- Ollama installed and running (`ollama serve` or systemd service)
- No API keys needed

## Instructions

1. **List installed models**:
   ```bash
   ollama list                    # name, size, modified date
   ollama show <model>            # detailed info (parameters, template, license)
   ```

2. **Pull / remove models**:
   ```bash
   ollama pull llama3.3:70b       # download a model
   ollama pull mistral:latest     # latest version
   ollama rm <model>              # remove (confirm with user first!)
   ```

3. **Benchmark a model**:
   ```bash
   # Time a response
   time ollama run <model> "Explain quantum computing in 3 sentences" --verbose 2>&1

   # Extract tokens/sec from verbose output
   ollama run <model> "Hello" --verbose 2>&1 | grep "eval rate"
   ```

4. **Compare models** β€” run same prompt across multiple models:
   ```
   ## πŸ“Š Ollama Model Benchmark
   **Prompt:** "Explain quantum computing in 3 sentences"
   **Hardware:** [CPU/GPU specs]

   | Model | Size | Tokens/sec | Response Time | Quality |
   |-------|------|-----------|--------------|---------|
   | llama3.3:8b | 4.7GB | 42 t/s | 2.1s | ⭐⭐⭐⭐ |
   | mistral:7b | 4.1GB | 48 t/s | 1.8s | ⭐⭐⭐ |
   | phi3:mini | 2.3GB | 65 t/s | 1.2s | ⭐⭐⭐ |
   ```

5. **Check Ollama status**:
   ```bash
   curl -s http://localhost:11434/api/tags | jq .    # API check
   systemctl status ollama                            # service status
   ollama ps                                          # running models
   ```

## Model Naming

Format: `name:tag` β€” e.g., `llama3.3:8b`, `mistral:latest`, `codellama:13b-instruct`

Common tags: `latest`, `7b`, `13b`, `70b`, `instruct`, `code`

## Edge Cases

- **Ollama not running**: Start with `ollama serve` or `systemctl start ollama`.
- **Insufficient disk space**: Check `df -h` before pulling large models. 70B models need ~40GB.
- **Insufficient RAM**: Models need RAM β‰ˆ model size. 7B β‰ˆ 8GB RAM, 70B β‰ˆ 48GB RAM.
- **GPU vs CPU**: Performance varies dramatically. Note hardware in benchmarks.
- **Model not found**: Check spelling. Use `ollama list` to see available names. Search at [ollama.com/library](https://ollama.com/library).
- **Slow downloads**: Large models take time. Use `ollama pull` with patience; it supports resume.

## Troubleshooting

- **Port 11434 in use**: Another Ollama instance may be running. `lsof -i :11434`.
- **CUDA errors**: Check GPU drivers with `nvidia-smi`. Reinstall Ollama if needed.
- **Model corrupted**: Remove and re-pull: `ollama rm <model> && ollama pull <model>`.

Files in this skill

  • README.md601 B
  • SKILL.md2.9 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…