How do I install the LLM Endpoint Demo skill?

Run npx skillmds@latest add xiaomimimo/llm-endpoint-demo in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is LLM Endpoint Demo safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with LLM Endpoint Demo?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is LLM Endpoint Demo free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published LLM Endpoint Demo?

xiaomimimo (@xiaomimimo) published this skill. Their other Agent Skills are listed on their SkillMD profile.

LLM Endpoint Demo by xiaomimimo — Agent Skill

Name: LLM Endpoint Demo
Author: xiaomimimo

LLM Endpoint Demo

Demo and end-to-end fixture for MiMoCode's temporary local LLM server. Use when verifying that a skill can borrow a configured chat model through a local base_url and a throwaway token instead of a real provider API key, or when testing the expire-and-reissue loop. Not a general-purpose skill.

xiaomimimo 99facd7 2 files · 5.9 KB Updated Sep 17, 2026

File contents

LLM endpoint demo

A minimal skill that needs "a model" and is given one without ever seeing a provider API key. It reads a handful of environment variables and calls an OpenAI-compatible endpoint; it knows nothing about MiMoCode's provider config or credential store.

Its purpose is to be a black-box witness. If this skill works, the claim "a skill can use a configured model without the secret entering the model's context or a readable config file" is demonstrated rather than asserted.

What this skill needs

Variable	Meaning
`OPENAI_BASE_URL`	The local endpoint, e.g. `http://127.0.0.1:53854/v1`
`OPENAI_API_KEY`	A temporary token, NOT a provider key
`OPENAI_MODEL`	A `provider/model` reference, e.g. `anthropic/claude-haiku-4-5`

Setting it up

Make sure a server is running for this project. Ask it:
```
<mimocode> llm-server status --json
```
<mimocode> is however THIS installation is invoked. Do not assume mimo is on PATH — it frequently is not, for example under npx or a source checkout. If nothing is running, start one in the background:
```
<mimocode> llm-server &
```
Prefer a fixed --port if the endpoint has to survive a restart, because the default port is chosen at random and base_url would otherwise change.
Mint a token scoped to this task.
```
<mimocode> llm-server issue --model <provider/model> --label llm-endpoint-demo --json
```
The response carries base_url, api_key, expires_at, and — importantly — renew_command / renew_argv, which is the invocation to use later for a replacement key. Keep it: it already encodes the flags that shaped this token, so a renewal is equivalent rather than merely valid.

Pass --model so the key cannot reach models this task has no business calling. One key may carry several --model flags. Pass --ttl none only for a job with no natural end.

Export and run.

OPENAI_BASE_URL=<base_url> OPENAI_API_KEY=<api_key> OPENAI_MODEL=<provider/model> \
  node summarize.mjs "one sentence about the sea"

Handling expiry

The token has a lifetime. It slides forward on every use, so an actively working task is not interrupted, but an idle one will age out.

The script exits with a distinct code so the failure is actionable:

Exit	Meaning	What to do
0	success	completion on stdout
2	`expired_api_key`	run `renew_argv`, replace `OPENAI_API_KEY`, retry once
3	other failure	report it; do not retry blindly
4	environment missing	go back to step 2

On exit code 2, base_url does not change — tokens live outside the server process, so only the key needs replacing. Do not restart the server and do not re-derive the endpoint.

What must never happen

A provider API key must never appear in OPENAI_API_KEY, in this skill's directory, or anywhere in the conversation. The whole point is that it stays inside MiMoCode.
The token must not be written into a committed file. It is short-lived and per-task; mint a fresh one instead of persisting it.

---name: llm-endpoint-demodescription: Demo and end-to-end fixture for MiMoCode's temporary local LLM server. Use when verifying that a skill can borrow a configured chat model through a local base_url and a throwaway token instead of a real provider API key, or when testing the expire-and-reissue loop. Not a general-purpose skill.---# LLM endpoint demoA minimal skill that needs "a model" and is given one **without ever seeing aprovider API key**. It reads a handful of environment variables and calls anOpenAI-compatible endpoint; it knows nothing about MiMoCode's provider config orcredential store.Its purpose is to be a black-box witness. If this skill works, the claim "a skillcan use a configured model without the secret entering the model's context or areadable config file" is demonstrated rather than asserted.## What this skill needs| Variable | Meaning || --- | --- || `OPENAI_BASE_URL` | The local endpoint, e.g. `http://127.0.0.1:53854/v1` || `OPENAI_API_KEY` | A temporary token, NOT a provider key || `OPENAI_MODEL` | A `provider/model` reference, e.g. `anthropic/claude-haiku-4-5` |## Setting it up1. **Make sure a server is running for this project.** Ask it: ``` <mimocode> llm-server status --json ``` `<mimocode>` is however THIS installation is invoked. Do not assume `mimo` is on `PATH` — it frequently is not, for example under `npx` or a source checkout. If nothing is running, start one in the background: ``` <mimocode> llm-server & ``` Prefer a fixed `--port` if the endpoint has to survive a restart, because the default port is chosen at random and `base_url` would otherwise change.2. **Mint a token scoped to this task.** ``` <mimocode> llm-server issue --model <provider/model> --label llm-endpoint-demo --json ``` The response carries `base_url`, `api_key`, `expires_at`, and — importantly — `renew_command` / `renew_argv`, which is the invocation to use later for a replacement key. Keep it: it already encodes the flags that shaped this token, so a renewal is equivalent rather than merely valid. Pass `--model` so the key cannot reach models this task has no business calling. One key may carry several `--model` flags. Pass `--ttl none` only for a job with no natural end.3. **Export and run.** ``` OPENAI_BASE_URL=<base_url> OPENAI_API_KEY=<api_key> OPENAI_MODEL=<provider/model> \ node summarize.mjs "one sentence about the sea" ```## Handling expiryThe token has a lifetime. It slides forward on every use, so an actively workingtask is not interrupted, but an idle one will age out.The script exits with a distinct code so the failure is actionable:| Exit | Meaning | What to do || --- | --- | --- || 0 | success | completion on stdout || 2 | `expired_api_key` | run `renew_argv`, replace `OPENAI_API_KEY`, retry once || 3 | other failure | report it; do not retry blindly || 4 | environment missing | go back to step 2 |On exit code 2, `base_url` does **not** change — tokens live outside the serverprocess, so only the key needs replacing. Do not restart the server and do notre-derive the endpoint.## What must never happen- A provider API key must never appear in `OPENAI_API_KEY`, in this skill's directory, or anywhere in the conversation. The whole point is that it stays inside MiMoCode.- The token must not be written into a committed file. It is short-lived and per-task; mint a fresh one instead of persisting it.

Frequently asked questions