CY

CyberStrike OffSec 35B

CyberstrikeGGUF by ahmedandaloesUpdated 2026-07-08
Download on Hugging Face
Parameters35.5B
Context256K
Layers41
Architectureqwen35moe
Smallest quant13.2 GB
Quick answer

CyberStrike OffSec 35B needs about 22.9 GB of memory at Q4_K_M (a 21.7 GB file) with an 8K context window, so it fits on a 24 GB GPU. This repository has 10 quants, from 13.2 GB (Q2_K) to 37.8 GB (Q8_0). Longer context needs more: at 32K tokens the KV cache alone adds about 2.8 GB.

CyberStrike OffSec 35B – a 35.5B Qwen3.6‑based model fine‑tuned for structured tool calls

CyberStrike OffSec 35B is a 35.5B‑parameter Qwen3.6‑based model fine‑tuned for autonomous offensive‑security agents. It emits real, structured tool calls in the exact format required by the CyberStrike harness. The model is released under Apache‑2.0 and is available as a single‑piece GGUF checkpoint.

Good at

  • Accurate tool‑call formatting
  • Clean termination of agent sessions
  • Alignment to CyberStrike harness

Limits

  • No vision support
  • Requires large VRAM for higher‑quality quants
  • No broad capability upgrade beyond tool use

Best for

  • Automated pentesting workflows
  • Tool‑calling harnesses
  • Security‑automation scripts

Who it’s for. Developers and security teams building or extending the CyberStrike agent framework. The model is intended for authorized offensive‑security work only and requires a compatible GGUF environment such as llama.cpp or Ollama.

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
Q2_K13.2 GB (3 parts) 14.4 GB
Too big Get file →
Q3_K_S15.5 GB (4 parts) 16.7 GB
Too big Get file →
Q3_K_M17.2 GB (4 parts) 18.4 GB
Too big Get file →
Q3_K_L18.6 GB (4 parts) 19.7 GB
Too big Get file →
Q4_K_S20.4 GB (5 parts) 21.6 GB
Too big Get file →
Q4_K_M21.7 GB (5 parts) 22.9 GB
Too big Get file →
Q5_K_S24.6 GB (6 parts) 25.8 GB
Too big Get file →
Q5_K_M25.3 GB (6 parts) 26.5 GB
Too big Get file →
Q6_K29.2 GB (6 parts) 30.4 GB
Too big Get file →
Q8_037.8 GB (8 parts) 39.0 GB
Too big Get file →

For 8 GB VRAM, use Q2_K (13.25 GB file, 14.4 GB memory at 8 k context). For 12 GB VRAM, Q3_K_S (15.55 GB file, 16.7 GB memory) or Q3_K_M (17.17 GB file, 18.4 GB memory). Higher‑quality quants such as Q4_K_M or Q5_K_M require 20–26 GB VRAM. All quants are split into multiple shards; download all shards for the chosen quant.

What GPU do you need for CyberStrike OffSec 35B?

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 Q2_K (13.2 GB file, about 14.4 GB in use).
  • 24 GB VRAM: the best quant that fits is Q4_K_M (21.7 GB file, about 22.9 GB in use).
  • 32 GB VRAM: the best quant that fits is Q6_K (29.2 GB file, about 30.4 GB in use).
  • 48 GB VRAM: the best quant that fits is Q8_0 (37.8 GB file, about 39.0 GB in use).

Which CyberStrike OffSec 35B quant should you choose?

Q4_K_M is the usual starting point for CyberStrike OffSec 35B: it balances file size and quality well. Here it is a 21.7 GB file.

The Q8_0 file is 37.8 GB, about 1.7 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 Q2_K at 13.2 GB, with the quality trade-offs that come with fewer bits. Use it only when memory is very tight. Expect a clear drop in quality, which is usually worse on small models and easier to live with on large ones.

New to quant names? Read GGUF quantization explained.

Specifications

Architecture from the GGUF header

Architectureqwen35moe
Parameters35.5B (approximate, mixture of experts)
Layers41
Trained context262,144 tokens
KV cache (fp16)82 KB per token

Source

Quantized byahmedandaloes
Licenseapache-2.0
Downloads (HF)2,858
Last updated2026-07-08

Frequently asked questions about CyberStrike OffSec 35B

How much VRAM does CyberStrike OffSec 35B need?

About 22.9 GB at Q4_K_M with an 8K context window. That is the 21.7 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 CyberStrike OffSec 35B on an 8 GB GPU?

Not at an 8K context. The smallest file needs about 14.4 GB, so you would need a larger GPU or CPU offloading.

What is the file size of CyberStrike OffSec 35B GGUF?

It depends on the quant: Q2_K is 13.2 GB, Q3_K_S is 15.5 GB, Q3_K_M is 17.2 GB, Q3_K_L is 18.6 GB, Q4_K_S is 20.4 GB, Q4_K_M is 21.7 GB and 4 more.

What context length does CyberStrike OffSec 35B support?

The GGUF header lists a trained context length of 262,144 tokens (256K). The KV cache grows with the context you use: about 0.7 GB at 8K and 2.8 GB at 32K.

Where can I download CyberStrike OffSec 35B GGUF?

The files are on Hugging Face in the ahmedandaloes/CyberStrike-OffSec-35B-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.

What license does CyberStrike OffSec 35B use?

Hugging Face lists the license as apache-2.0. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.

Can I run CyberStrike OffSec 35B on 8 GB VRAM?

Yes, the Q2_K quant uses 13.25 GB file size and requires approximately 14.4 GB VRAM at 8 k context.

Does this model support vision or image inputs?

No, the model is text‑only and does not support vision.

What license applies to this model?

The model is released under the Apache‑2.0 license.

Other GGUFs of CyberStrike-OffSec-35B

Similar models

Browse all →

More Cyberstrike models

All Cyberstrike →

Other large models

All large models →