MO

modelaudit gguf array chat template poc

ModelauditGGUF by celvexgroupUpdated 2026-07-19
Download on Hugging Face
Parameters—
Context—
Layers—
Architecturellama
Smallest quant0.0 GB
Quick answer

modelaudit gguf array chat template poc needs about 0.5 GB of memory at its main file (a 0.0 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 3 quants, from 0.0 GB to 0.0 GB.

Modelaudit GGUF array chat template PoC – a proof‑of‑concept for SSTI detection bypass

This GGUF model is a proof‑of‑concept demonstrating a metadata value‑type confusion that bypasses the Jinja2 SSTI detector in llama.cpp. It contains three identical files with unknown quantization and a 0.5 GB memory estimate at 8 k context. The model is not intended for production use.

Good at

  • SSTI detection bypass demonstration
  • LLM chat template handling
  • Metadata value‑type testing

Limits

  • No trained context tokens provided
  • No license specified
  • Not a full language model

Best for

  • Security researchers testing SSTI scanners
  • LLM developers debugging chat templates
  • Academic studies on metadata handling

Who it’s for. Security analysts and LLM developers who need a controlled environment to test chat template parsing and SSTI detection mechanisms. The model is a minimal, non‑functional example and should not be used for general inference.

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
—0.0 GB 0.5 GB
Fits Get file →
—0.0 GB 0.5 GB
Fits Get file →
—0.0 GB 0.5 GB
Fits Get file →

All three files are listed with unknown quantization. The memory estimate is 0.5 GB at 8 k context, which is approximate. For a 4 GB VRAM system, any of the files should run comfortably. If a smaller VRAM budget is required, consider using a lower‑precision quantization if available, but no such quant is listed.

What GPU do you need for modelaudit gguf array chat template poc?

These figures add the file size, an fp16 KV cache at an 8K context window 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: the best quant that fits is the main file (0.0 GB file, about 0.5 GB in use).

Which modelaudit gguf array chat template poc quant should you choose?

If memory is tight, the smallest file is the first one in the table at 0.0 GB, with the quality trade-offs that come with fewer bits.

New to quant names? Read GGUF quantization explained.

Specifications

Architecture from the GGUF header

Architecturellama

Source

Quantized bycelvexgroup
Downloads (HF)66
Last updated2026-07-19

Frequently asked questions about modelaudit gguf array chat template poc

How much VRAM does modelaudit gguf array chat template poc need?

About 0.5 GB at its main file with an 8K context window. That is the 0.0 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 modelaudit gguf array chat template poc on an 8 GB GPU?

Yes, with the smaller files: the 0.0 GB file needs about 0.5 GB at 8K context. Larger quants in this repository do not fit in 8 GB.

What is the file size of modelaudit gguf array chat template poc GGUF?

It depends on the quant: file is 0.0 GB, file is 0.0 GB, file is 0.0 GB.

Where can I download modelaudit gguf array chat template poc GGUF?

The files are on Hugging Face in the celvexgroup/modelaudit-gguf-array-chat-template-poc repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.

Can I run this model on 4 GB VRAM?

Yes, the estimated memory usage is 0.5 GB at 8 k context, so it fits easily in a 4 GB VRAM system.

Does this model support vision or other modalities?

No, the model contains only chat template data and does not provide vision or other modality support.

Is this model licensed for commercial use?

The license field is empty; use it only for research or educational purposes and verify compliance with any applicable terms.

More from celvexgroup

All by celvexgroup →