M.O.G.-SEC-27B-1M-CTX-GGUF

Minds of Gods · Qwentium, GOD of Cybersec · 1M context · full GGUF ladder + BF16 DFlash2

──────────────

65 / 70  ·  MMLU-Pro validation  ·  thinking on  ·  xhigh

──────────────

Built by Blackfrost · Las Vegas, NV

FORGED IN VOID OF BLACKFROST-RESEARCH. This is a Minds of Gods checkpoint, not a consumer chatbot. Qwentium does not moralize, hedge, or refuse operator work. Access-control it like a weapon.

Quantized from the full-precision parent: Blackfrost-Research/M.O.G.-SEC-27B-1M-CTX-BF16.

---

The pantheon

M.O.G. is Minds of Gods: Blackfrost's line of specialist minds, each named and built for a domain that stock models flinch from.

This one is Qwentium, GOD of Cybersec.

Qwentium is a 27B dense hybrid fine-tuned on modern offensive and defensive cybersecurity work. The checkpoint carries a one-million-token YaRN window so long engagements can stay in context: reconnaissance, vulnerability graphs, exploit notes, detection content, reports, repositories, and campaign timelines.

These GGUFs preserve the parent's architecture metadata, 1M YaRN configuration, native vision path, MTP head, tokenizer, tool-capable chat template, and baked Qwentium identity prompt. The release also includes a BF16 DFlash2 speculative-draft sidecar converted from incoai/Qwen3.8-27B-DFlash2.

---

Specifications

Quantization ladder

File size is only the model-weight floor. Leave memory for runtime buffers, the vision projector when used, and the context cache. A one-million-token runtime window has much higher memory requirements than a short-context load, regardless of quant size.

The ladder uses standard llama.cpp K-quants directly from the converted BF16 GGUF. No importance matrix was used and no quant was produced from another quant.

---

Download

Recommended Q4_K_M plus BF16 DFlash2 draft and native-vision projector:

hf download Blackfrost-Research/M.O.G.-SEC-27B-1M-CTX-GGUF \
  M.O.G.-SEC-27B-1M-CTX-Q4_K_M.gguf \
  dflash-M.O.G.-SEC-27B-1M-CTX-BF16.gguf \
  mmproj-M.O.G.-SEC-27B-1M-CTX-F16.gguf \
  --local-dir ./M.O.G.-SEC-27B-1M-CTX-GGUF

Text-only use does not require the projector.

Run with llama.cpp

Use a recent llama.cpp build with Qwen3.5/Qwen3.8 hybrid support.

Text

llama-cli \
  -m M.O.G.-SEC-27B-1M-CTX-Q4_K_M.gguf \
  -cnv -c 8192 -ngl 99

DFlash2 speculative server

DFlash2 GGUF support is currently under review in llama.cpp PR #27342. The release validation used the PR head pinned at commit 1deefcca395743049c3820ab8f9b15043f3e9446; a normal build without that change cannot load this DFlash2 sidecar yet.

Build that revision, then serve the recommended target/draft pair:

git clone https://github.com/ggml-org/llama.cpp
cd llama.cpp
git fetch origin pull/27342/head:dflash2
git checkout 1deefcca395743049c3820ab8f9b15043f3e9446
cmake -S . -B build -DGGML_CUDA=ON -DCMAKE_BUILD_TYPE=Release
cmake --build build --config Release -j --target llama-server

./build/bin/llama-server \
  -m M.O.G.-SEC-27B-1M-CTX-Q4_K_M.gguf \
  --spec-draft-model dflash-M.O.G.-SEC-27B-1M-CTX-BF16.gguf \
  --spec-type draft-dflash \
  --spec-draft-n-max 3 \
  --spec-draft-n-min 0 \
  --spec-draft-p-min 0 \
  -ngl all -ngld all \
  --device CUDA0 --spec-draft-device CUDA0 \
  --split-mode none --main-gpu 0 \
  -c 1000000 -ctk q8_0 -ctv q8_0 \
  --spec-draft-type-k f16 --spec-draft-type-v f16 \
  -fa on --parallel 1 --jinja \
  --host 0.0.0.0 --port 8001

Draft length 3 was selected by a local sweep of 2, 3, 4, and 7 tokens. The draft checkpoint's native context metadata is 262,144 tokens; using the sidecar beyond that range with the 1M target is experimental even though the target retains its full 1M YaRN metadata.

Vision

llama-cli \
  -m M.O.G.-SEC-27B-1M-CTX-Q4_K_M.gguf \
  -mm mmproj-M.O.G.-SEC-27B-1M-CTX-F16.gguf \
  --image ./your-image.jpg \
  -p "Describe this image." \
  -cnv -c 8192 -ngl 99

The embedded template enables thinking by default. To disable it in current llama.cpp builds, add:

-rea off

One-million-token context

The GGUF metadata preserves the parent recipe:

context_length:                    1000000
rope.scaling.type:                 yarn
rope.scaling.factor:               4.0
rope.scaling.original_context:     262144
rope.freq_base:                    10000000
rope.dimension_sections:           11,11,10,0

Request the full window with -c 1000000. This is a hardware-heavy configuration: choose cache types, GPU offload, and tensor split for your system. The release validation below used short contexts; preserving the 1M metadata is not a claim that every llama.cpp backend or host can allocate and run the full window.

---

Validation

All twelve GGUF artifacts were structurally checked after conversion:

• Ten text quants: qwen35, 866 tensors, 65 blocks, one MTP/NextN layer
• Context: 1,000,000; YaRN factor 4.0; original context 262,144
• MRoPE sections: [11, 11, 10, 0]
• Embedded Qwentium template: 13,427 characters, identical across the ladder
• Vision projector: qwen3vl_merger, F16, 334 tensors
• DFlash2 draft: dflash, 81 tensors, BF16 weights, block 8, selector rank 256/top-k 16, dynamic convolution kernel 2/group 16, target layers [6, 20, 34, 48, 62]

Q4_K_M was then smoke-tested with a local CUDA llama.cpp build on 4x NVIDIA RTX PRO 6000 Blackwell GPUs:

These are single smoke runs on a busy shared host, not formal performance benchmarks.

The Q4_K_M target plus BF16 DFlash2 sidecar was also tested through the OpenAI-compatible llama.cpp server on one NVIDIA RTX PRO 6000 Blackwell 96 GB GPU. The server allocated the full 1,000,000-token target context with Q8_0 target KV, used one slot, temperature 0, thinking disabled, and draft length 3. Each topic generated 256 tokens:

The measured acceptance gate was 49 tok/s from the prior clean-BF16 service. This GGUF configuration cleared it by 82.6% (1.83x). That comparison is an operational gate, not an engine-isolated benchmark: the prior service used a different precision/runtime/GPU topology. Results will vary with prompt distribution, backend, context occupancy, and sampling.

SHA-256 hashes for every GGUF are in SHA256SUMS.

---

Measured parent capability

The following results are inherited from the BF16 parent's model card. Capability and refusal benches were measured on its NVFP4 child, not independently on every GGUF quant. Quantization can change scores; reproduce on the exact file you deploy.

The source protocol and complete tables are documented on the BF16 parent card.

---

What Qwentium is for

• Adversary emulation, exploit reasoning, payload and tradecraft writeups
• Detection engineering, hunting queries, control gaps, and incident-response narrative
• Long-context case files: repositories, pcaps-as-text, ticket storms, and campaign timelines
• Operator work where refusal is the failure mode

This is not a public assistant and not a claim that every answer is correct. Validate outputs, isolate the runtime, control access, and use it only within your authorization and applicable law.

Notes and limitations

• The full ladder preserves the parent's one-layer MTP head. Standard inference works without a separate draft model; no GGUF MTP speedup is claimed here.
• The optional DFlash2 sidecar is a distinct speculative path and currently requires the pinned llama.cpp PR above. It was validated for text generation only.
• Native image/video input requires the included F16 projector and a compatible llama.cpp multimodal build.
• The model's custom template is Jinja-based and carries baked system identity, reasoning controls, tool-call formatting, and multimodal handling.
• Very low-bit quants trade capability for footprint. Q4_K_M or higher is recommended for demanding cyber work.
• The 1M context setting is static YaRN. Short-context behavior may differ from the native-context parent.

License

Apache-2.0, following the parent checkpoint. Review the parent model card and the base model's terms before deployment.