Instructions to use StevenMD/Phi-4-mini-instruct-fixed-tokenizer-and-model with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- llama-cpp-python
How to use StevenMD/Phi-4-mini-instruct-fixed-tokenizer-and-model with llama-cpp-python:
# !pip install llama-cpp-python from llama_cpp import Llama llm = Llama.from_pretrained( repo_id="StevenMD/Phi-4-mini-instruct-fixed-tokenizer-and-model", filename="phi4-mini-Q8_0.gguf", )
output = llm( "Once upon a time,", max_tokens=512, echo=True ) print(output)
- Notebooks
- Google Colab
- Kaggle
- Local Apps
- llama.cpp
How to use StevenMD/Phi-4-mini-instruct-fixed-tokenizer-and-model with llama.cpp:
Install from brew
brew install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama-server -hf StevenMD/Phi-4-mini-instruct-fixed-tokenizer-and-model:Q8_0 # Run inference directly in the terminal: llama-cli -hf StevenMD/Phi-4-mini-instruct-fixed-tokenizer-and-model:Q8_0
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama-server -hf StevenMD/Phi-4-mini-instruct-fixed-tokenizer-and-model:Q8_0 # Run inference directly in the terminal: llama-cli -hf StevenMD/Phi-4-mini-instruct-fixed-tokenizer-and-model:Q8_0
Use pre-built binary
# Download pre-built binary from: # https://github.com/ggerganov/llama.cpp/releases # Start a local OpenAI-compatible server with a web UI: ./llama-server -hf StevenMD/Phi-4-mini-instruct-fixed-tokenizer-and-model:Q8_0 # Run inference directly in the terminal: ./llama-cli -hf StevenMD/Phi-4-mini-instruct-fixed-tokenizer-and-model:Q8_0
Build from source code
git clone https://github.com/ggerganov/llama.cpp.git cd llama.cpp cmake -B build cmake --build build -j --target llama-server llama-cli # Start a local OpenAI-compatible server with a web UI: ./build/bin/llama-server -hf StevenMD/Phi-4-mini-instruct-fixed-tokenizer-and-model:Q8_0 # Run inference directly in the terminal: ./build/bin/llama-cli -hf StevenMD/Phi-4-mini-instruct-fixed-tokenizer-and-model:Q8_0
Use Docker
docker model run hf.co/StevenMD/Phi-4-mini-instruct-fixed-tokenizer-and-model:Q8_0
- LM Studio
- Jan
- Ollama
How to use StevenMD/Phi-4-mini-instruct-fixed-tokenizer-and-model with Ollama:
ollama run hf.co/StevenMD/Phi-4-mini-instruct-fixed-tokenizer-and-model:Q8_0
- Unsloth Studio new
How to use StevenMD/Phi-4-mini-instruct-fixed-tokenizer-and-model with Unsloth Studio:
Install Unsloth Studio (macOS, Linux, WSL)
curl -fsSL https://unsloth.ai/install.sh | sh # Run unsloth studio unsloth studio -H 0.0.0.0 -p 8888 # Then open http://localhost:8888 in your browser # Search for StevenMD/Phi-4-mini-instruct-fixed-tokenizer-and-model to start chatting
Install Unsloth Studio (Windows)
irm https://unsloth.ai/install.ps1 | iex # Run unsloth studio unsloth studio -H 0.0.0.0 -p 8888 # Then open http://localhost:8888 in your browser # Search for StevenMD/Phi-4-mini-instruct-fixed-tokenizer-and-model to start chatting
Using HuggingFace Spaces for Unsloth
# No setup required # Open https://huggingface.co/spaces/unsloth/studio in your browser # Search for StevenMD/Phi-4-mini-instruct-fixed-tokenizer-and-model to start chatting
- Docker Model Runner
How to use StevenMD/Phi-4-mini-instruct-fixed-tokenizer-and-model with Docker Model Runner:
docker model run hf.co/StevenMD/Phi-4-mini-instruct-fixed-tokenizer-and-model:Q8_0
- Lemonade
How to use StevenMD/Phi-4-mini-instruct-fixed-tokenizer-and-model with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull StevenMD/Phi-4-mini-instruct-fixed-tokenizer-and-model:Q8_0
Run and chat with the model
lemonade run user.Phi-4-mini-instruct-fixed-tokenizer-and-model-Q8_0
List all available models
lemonade list
Copied original model file: SECURITY.md
Browse files- SECURITY.md +41 -0
SECURITY.md
ADDED
|
@@ -0,0 +1,41 @@
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<!-- BEGIN MICROSOFT SECURITY.MD V0.0.9 BLOCK -->
|
| 2 |
+
|
| 3 |
+
## Security
|
| 4 |
+
|
| 5 |
+
Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/Microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet) and [Xamarin](https://github.com/xamarin).
|
| 6 |
+
|
| 7 |
+
If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://aka.ms/security.md/definition), please report it to us as described below.
|
| 8 |
+
|
| 9 |
+
## Reporting Security Issues
|
| 10 |
+
|
| 11 |
+
**Please do not report security vulnerabilities through public GitHub issues.**
|
| 12 |
+
|
| 13 |
+
Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://aka.ms/security.md/msrc/create-report).
|
| 14 |
+
|
| 15 |
+
If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com). If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://aka.ms/security.md/msrc/pgp).
|
| 16 |
+
|
| 17 |
+
You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://www.microsoft.com/msrc).
|
| 18 |
+
|
| 19 |
+
Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
|
| 20 |
+
|
| 21 |
+
* Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
|
| 22 |
+
* Full paths of source file(s) related to the manifestation of the issue
|
| 23 |
+
* The location of the affected source code (tag/branch/commit or direct URL)
|
| 24 |
+
* Any special configuration required to reproduce the issue
|
| 25 |
+
* Step-by-step instructions to reproduce the issue
|
| 26 |
+
* Proof-of-concept or exploit code (if possible)
|
| 27 |
+
* Impact of the issue, including how an attacker might exploit the issue
|
| 28 |
+
|
| 29 |
+
This information will help us triage your report more quickly.
|
| 30 |
+
|
| 31 |
+
If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://aka.ms/security.md/msrc/bounty) page for more details about our active programs.
|
| 32 |
+
|
| 33 |
+
## Preferred Languages
|
| 34 |
+
|
| 35 |
+
We prefer all communications to be in English.
|
| 36 |
+
|
| 37 |
+
## Policy
|
| 38 |
+
|
| 39 |
+
Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://aka.ms/security.md/cvd).
|
| 40 |
+
|
| 41 |
+
<!-- END MICROSOFT SECURITY.MD BLOCK -->
|