GPT OSS Cybersecurity 20B Merged Informed Abliterated needs about 16.7 GB of memory at Q4_K_M (a 15.8 GB file) with an 8K context window, so it fits on a 24 GB GPU. This repository has 12 quants, from 12.1 GB (Q3_K_S) to 22.3 GB (Q8_0). Longer context needs more: at 32K tokens the KV cache alone adds about 1.6 GB.
20.9B parameter GPT‑OSS cybersecurity model
GPT‑OSS Cybersecurity 20B Merged Informed Abliterated is a 20.9B parameter model trained on 131072 context tokens. It supports tool usage and is a mixture of experts. The model is available in multiple GGUF quantizations.
Good at
- Tool usage
- Cybersecurity text generation
- Large context handling
Limits
- No vision support
- License not specified
- Large VRAM requirement for higher quants
Best for
- Security policy drafting
- Incident response simulations
- Threat analysis reports
Who it’s for. Developers and security analysts needing a large‑context LLM for cybersecurity tasks. The model is suitable for environments where tool integration is required.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q3_K_S | 12.1 GB | 13.0 GB | Too big | Get file → | |
| Q2_K | 12.1 GB | 13.0 GB | Too big | Get file → | |
| MXFP4_MOE | 12.1 GB | 13.0 GB | Too big | Get file → | |
| IQ4_XS | 12.2 GB | 13.1 GB | Too big | Get file → | |
| Q3_K_M | 12.9 GB | 13.8 GB | Too big | Get file → | |
| Q3_K_L | 13.3 GB | 14.2 GB | Too big | Get file → | |
| Q4_K_S | 14.7 GB | 15.6 GB | Too big | Get file → | |
| Q4_K_M | 15.8 GB | 16.7 GB | Too big | Get file → | |
| Q5_K_S | 15.9 GB | 16.8 GB | Too big | Get file → | |
| Q5_K_M | 16.9 GB | 17.8 GB | Too big | Get file → | |
| Q6_K | 22.2 GB | 23.1 GB | Too big | Get file → | |
| Q8_0 | 22.3 GB | 23.2 GB | Too big | Get file → |
For 8 GB VRAM, use Q3_K_S (file size 12.06 GB, estimated 13 GB memory). For 12 GB VRAM, Q4_K_M (15.81 GB, 16.7 GB memory) is a good balance. For 16 GB VRAM, Q5_K_M (16.89 GB, 17.8 GB memory) offers higher quality.
What GPU do you need for GPT OSS Cybersecurity 20B Merged Informed Abliterated?
These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.
- 4 GB VRAM: no quant fits at an 8K context.
- 6 GB VRAM: no quant fits at an 8K context.
- 8 GB VRAM: no quant fits at an 8K context.
- 12 GB VRAM: no quant fits at an 8K context.
- 16 GB VRAM: the best quant that fits is Q4_K_S (14.7 GB file, about 15.6 GB in use).
- 24 GB VRAM: the best quant that fits is Q8_0 (22.3 GB file, about 23.2 GB in use).
Which GPT OSS Cybersecurity 20B Merged Informed Abliterated quant should you choose?
Q4_K_M is the usual starting point for GPT OSS Cybersecurity 20B Merged Informed Abliterated: it balances file size and quality well. Here it is a 15.8 GB file.
The Q8_0 file is 22.3 GB, about 1.4 times the size of Q4_K_M. It keeps the weights closer to the original, which only matters if you have the memory to spare.
If memory is tight, the smallest file is Q3_K_S at 12.1 GB, with the quality trade-offs that come with fewer bits. A reasonable choice when a 4-bit file will not fit, mostly on larger models. Quality loss is noticeable but often acceptable.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Frequently asked questions about GPT OSS Cybersecurity 20B Merged Informed Abliterated
How much VRAM does GPT OSS Cybersecurity 20B Merged Informed Abliterated need?
About 16.7 GB at Q4_K_M with an 8K context window. That is the 15.8 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.
Can I run GPT OSS Cybersecurity 20B Merged Informed Abliterated on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 13.0 GB, so you would need a larger GPU or CPU offloading.
What is the file size of GPT OSS Cybersecurity 20B Merged Informed Abliterated GGUF?
It depends on the quant: Q3_K_S is 12.1 GB, Q2_K is 12.1 GB, MXFP4_MOE is 12.1 GB, IQ4_XS is 12.2 GB, Q3_K_M is 12.9 GB, Q3_K_L is 13.3 GB and 6 more.
What context length does GPT OSS Cybersecurity 20B Merged Informed Abliterated support?
The GGUF header lists a trained context length of 131,072 tokens (128K). The KV cache grows with the context you use: about 0.4 GB at 8K and 1.6 GB at 32K.
Where can I download GPT OSS Cybersecurity 20B Merged Informed Abliterated GGUF?
The files are on Hugging Face in the mradermacher/GPT-OSS-Cybersecurity-20B-Merged-informed-abliterated-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
Can I run Q4_K_M on 8 GB VRAM?
No, Q4_K_M requires about 16.7 GB memory at 8k context, exceeding 8 GB VRAM.
Which quant is best for limited VRAM?
Q3_K_S or Q2_K provide the smallest file sizes and lowest memory usage, suitable for 8–12 GB VRAM.
Does the model support vision?
No, the model does not include vision capabilities.