Safetensors
GGUF
qwen3
cybersecurity
agentic
red-team
blue-team
distillation
glm-5.2
kimi-k3
function-calling
tool-calling
tool-use
conversational
Instructions to use bebrws/security-8b with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- llama.cpp
How to use bebrws/security-8b with llama.cpp:
Install (macOS, Linux)
curl -LsSf https://llama.app/install.sh | sh # Start a local OpenAI-compatible server with a web UI: llama serve -hf bebrws/security-8b:Q4_K_M # Run inference directly in the terminal: llama cli -hf bebrws/security-8b:Q4_K_M
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama serve -hf bebrws/security-8b:Q4_K_M # Run inference directly in the terminal: llama cli -hf bebrws/security-8b:Q4_K_M
Build from source code
git clone https://github.com/ggml-org/llama.cpp.git cd llama.cpp cmake -B build cmake --build build -j --target llama-app # Start a local OpenAI-compatible server with a web UI: ./build/bin/llama serve -hf bebrws/security-8b:Q4_K_M # Run inference directly in the terminal: ./build/bin/llama cli -hf bebrws/security-8b:Q4_K_M
Use Docker
docker model run hf.co/bebrws/security-8b:Q4_K_M
- Llama new
- LM Studio
- Jan
- Ollama
How to use bebrws/security-8b with Ollama:
ollama run hf.co/bebrws/security-8b:Q4_K_M
- Unsloth Desktop
- Pi
How to use bebrws/security-8b with Pi:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf bebrws/security-8b:Q4_K_M
Configure the model in Pi
# Install Pi: npm install -g @earendil-works/pi-coding-agent # Add to ~/.pi/agent/models.json: { "providers": { "llama-cpp": { "baseUrl": "http://localhost:8080/v1", "api": "openai-completions", "apiKey": "none", "models": [ { "id": "bebrws/security-8b:Q4_K_M" } ] } } }Run Pi
# Start Pi in your project directory: pi
- Docker Model Runner
How to use bebrws/security-8b with Docker Model Runner:
docker model run hf.co/bebrws/security-8b:Q4_K_M
- Lemonade
How to use bebrws/security-8b with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull bebrws/security-8b:Q4_K_M
Run and chat with the model
lemonade run user.security-8b-Q4_K_M
List all available models
lemonade list
- Hermes Agent
How to use bebrws/security-8b with Hermes Agent:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf bebrws/security-8b:Q4_K_M
Configure Hermes
# Install Hermes: curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash hermes setup # Point Hermes at the local server: hermes config set model.provider custom hermes config set model.base_url http://127.0.0.1:8080/v1 hermes config set model.default bebrws/security-8b:Q4_K_M
Run Hermes
hermes
- Atomic Chat
- OpenClaw
How to use bebrws/security-8b with OpenClaw:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf bebrws/security-8b:Q4_K_M
Configure OpenClaw
# Install OpenClaw: npm install -g openclaw@latest # Register the local server and set it as the default model: openclaw onboard --non-interactive --mode local \ --auth-choice custom-api-key \ --custom-base-url http://127.0.0.1:8080/v1 \ --custom-model-id "bebrws/security-8b:Q4_K_M" \ --custom-provider-id llama-cpp \ --custom-compatibility openai \ --custom-text-input \ --accept-risk \ --skip-health
Run OpenClaw
openclaw agent --local --agent main --message "Hello from Hugging Face"
Model card: add Foundation-Sec-1.1-8B-Instruct comparison (honest standings)
Browse files
README.md
CHANGED
|
@@ -84,10 +84,12 @@ style, upsampled) produced churn without net gain and a chat-mode regression —
|
|
| 84 |
diagnosed as format conflict + template overfitting + step-share dilution. Round 7
|
| 85 |
fixed all three (bare-letter format-matched training, GLM-5.2 paraphrases,
|
| 86 |
multi-turn packing to 38% of gradient steps): chat CTI-Bench **+1.6** to 60.4%,
|
| 87 |
-
CyberMetric completion **87.8%** and SecQA completion **98.6%** (k3 records)
|
| 88 |
-
|
| 89 |
-
|
| 90 |
-
|
|
|
|
|
|
|
| 91 |
|
| 92 |
**Qualitative** (6 open-ended security prompts): Foundation-Sec gives terse,
|
| 93 |
mostly-correct completion-style answers; k3 gives structured markdown answers with
|
|
|
|
| 84 |
diagnosed as format conflict + template overfitting + step-share dilution. Round 7
|
| 85 |
fixed all three (bare-letter format-matched training, GLM-5.2 paraphrases,
|
| 86 |
multi-turn packing to 38% of gradient steps): chat CTI-Bench **+1.6** to 60.4%,
|
| 87 |
+
CyberMetric completion **87.8%** and SecQA completion **98.6%** (k3 records).
|
| 88 |
+
Against the base Foundation-Sec, v7cti-completion ties overall (79.26% vs 79.09%);
|
| 89 |
+
against the stronger **Foundation-Sec-1.1-8B-Instruct (80.50% overall)** k3 leads
|
| 90 |
+
only on CyberMetric (+2.0) and trails on CTI-Bench (62.6% vs 67.4%) — CTI/ATT&CK
|
| 91 |
+
knowledge remains a pretraining-data advantage and the target of the next round
|
| 92 |
+
(light domain CPT, then failure-targeted DPO).
|
| 93 |
|
| 94 |
**Qualitative** (6 open-ended security prompts): Foundation-Sec gives terse,
|
| 95 |
mostly-correct completion-style answers; k3 gives structured markdown answers with
|