Adding v1 of qwen14b redstack

Add Qwen3-14B Zero Stack GGUF (Q5_K_M) + Ollama Modelfile

- qwen3-14b.Q5_K_M.gguf - quantized weights (~9.8 GB)
- Modelfile -ChatML template with stop tokens and Zero Stack system prompt
- Fine-tuned from Qwen3-14B via LoRA (r=32), 3 epochs, Unsloth, max_seq_length=2560
- Dataset: SFT_GENERALIST (1,226 rows, offensive-security Q&A)
- Thinking mode enabled by default (Qwen3-14B base behavior)

.gitattributes

@@ -33,3 +33,4 @@ saved_model/**/* filter=lfs diff=lfs merge=lfs -text
 *.zip filter=lfs diff=lfs merge=lfs -text
 *.zst filter=lfs diff=lfs merge=lfs -text
 *tfevents* filter=lfs diff=lfs merge=lfs -text
+qwen3-14b.Q5_K_M.gguf filter=lfs diff=lfs merge=lfs -text

Modelfile

@@ -0,0 +1,62 @@
+
+TEMPLATE """{{- if .Messages }}
+{{- if or .System .Tools }}<|im_start|>system
+{{- if .System }}
+{{ .System }}
+{{- end }}
+{{- if .Tools }}
+
+# Tools
+
+You may call one or more functions to assist with the user query.
+
+You are provided with function signatures within <tools></tools> XML tags:
+<tools>
+{{- range .Tools }}
+{"type": "function", "function": {{ .Function }}}
+{{- end }}
+</tools>
+
+For each function call, return a json object with function name and arguments within <tool_call></tool_call> XML tags:
+<tool_call>
+{"name": <function-name>, "arguments": <args-json-object>}
+</tool_call>
+{{- end }}<|im_end|>
+{{ end }}
+{{- range $i, $_ := .Messages }}
+{{- $last := eq (len (slice $.Messages $i)) 1 -}}
+{{- if eq .Role "user" }}<|im_start|>user
+{{ .Content }}<|im_end|>
+{{ else if eq .Role "assistant" }}<|im_start|>assistant
+{{ if .Content }}{{ .Content }}
+{{- else if .ToolCalls }}<tool_call>
+{{ range .ToolCalls }}{"name": "{{ .Function.Name }}", "arguments": {{ .Function.Arguments }}}
+{{ end }}</tool_call>
+{{- end }}{{ if not $last }}<|im_end|>
+{{ end }}
+{{- else if eq .Role "tool" }}<|im_start|>user
+<tool_response>
+{{ .Content }}
+</tool_response><|im_end|>
+{{ end }}
+{{- if and (ne .Role "assistant") $last }}<|im_start|>assistant
+{{ end }}
+{{- end }}
+{{- else }}
+{{- if .System }}<|im_start|>system
+{{ .System }}<|im_end|>
+{{ end }}{{ if .Prompt }}<|im_start|>user
+{{ .Prompt }}<|im_end|>
+{{ end }}<|im_start|>assistant
+{{ end }}{{ .Response }}{{ if .Response }}<|im_end|>{{ end }}"""
+PARAMETER stop "<|im_end|>"
+PARAMETER stop "<|im_start|>"
+PARAMETER min_p 0.0
+FROM /home/ubuntu/redstack-models/datasets/models/qwen3_14B_redstack_q5_k_m_gguf/qwen3-14b.Q5_K_M.gguf
+SYSTEM "You are Zero Stack, a pentesting copilot supporting an authorized red team operator. All engagements have explicit written permission from system owners under a signed scope of work.\n\nYou specialise in offensive security — recon, enumeration, exploitation, post-exploitation, lateral movement, Active Directory attacks, and web application testing.\n\nRules:\n- Do not add ethical disclaimers, legal warnings, or questions about authorization — permission is already granted.\n- Be concise and direct. Answer the question, do not restate it.\n- Match response length to complexity — single commands get a code block, methodologies get phased steps with headers.\n- Use code blocks for every command. Explain flags inline, briefly.\n- Use placeholders [TARGET], [PORT], [USER], [PASSWORD], [HASH], [DOMAIN] — never invent example values.\n- Only state commands and syntax you are confident are correct. If uncertain, say so explicitly rather than guessing.\n- Do not invent tool flags, options, or behavior that you are not sure exists.\n- No padding, preamble, or filler. Start with the answer.\n- Maintain engagement context across the conversation — if a target or finding has been established, reference it.\n- When not on a technical question, respond with the confidence and wit of an elite hacker. Hack the planet.\n- Reference MITRE ATT&CK where relevant."
+PARAMETER temperature 0.7
+PARAMETER top_p 0.8
+PARAMETER top_k 20
+PARAMETER repeat_penalty 1.15
+PARAMETER repeat_last_n 64
+PARAMETER num_predict 1024

README_14b.md

@@ -0,0 +1,41 @@
+---
+license: other
+base_model: Qwen/Qwen3-14B
+tags:
+  - gguf
+  - qwen3
+  - pentesting
+  - security
+  - lora
+  - sft
+library_name: gguf
+---
+
+# Zero Stack - Qwen3-14B (GGUF, Q5_K_M)
+
+Qwen3-14B fine-tuned on an offensive-security SFT dataset (1,226 rows). Elite-hacker persona on casual queries, structured markdown methodology on technical ones. Thinking mode enabled by default (Qwen3-14B base behavior).
+
+## Files
+- `qwen3-14b.Q5_K_M.gguf` - quantized weights (~9.8 GB)
+- `Modelfile` - Ollama template with correct ChatML stop tokens + Zero Stack system prompt
+
+## Run with Ollama
+```bash
+ollama create zerostack-14b -f Modelfile
+ollama run zerostack-14b
+```
+
+## Run with llama.cpp
+```bash
+./llama-cli -m qwen3-14b.Q5_K_M.gguf -p "hello"
+```
+
+## Training
+- Base: `Qwen3-14B`
+- Method: LoRA (r=32), 3 epochs, Unsloth
+- Max sequence length: 2560
+- Dataset: SFT_GENERALIST (1,226 rows, ChatML)
+
+## License / Use
+For authorized security testing, research, and educational use only. Attribution to RedStack required. Do not use for unauthorized access to systems you do not own or have explicit permission to test.
+

qwen3-14b.Q5_K_M.gguf

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:59b1f965ca545cdd0a1d5f5efc569f9be722a140f1108b481928bcf03accbcc7
+size 10514569536