Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add rhtevan/agentfs --skill litellm-proxy-statusgit clone --depth 1 https://github.com/rhtevan/agentfsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/rhtevan/agentfs/litellm-proxy-status)<a href="https://agentmods.dev/skills/rhtevan/agentfs/litellm-proxy-status"><img src="https://agentmods.dev/badge/skills/rhtevan/agentfs/litellm-proxy-status/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/rhtevan/agentfs/litellm-proxy-status"><img src="https://agentmods.dev/badge/skills/rhtevan/agentfs/litellm-proxy-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00022 | $0.00539 |
| Opus 5.5 | $0.00009 | $0.00216 |
| Sonnet 5.5 | $0.00004 | $0.00108 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade C, and why
litellm-proxy-status scanned grade C with 2 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -s http://127.0.0.1:4000/health | python3 -m json.tool Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://127.0.0.1:4000/health | python3 -m json.tool What it actually says
LiteLLM Proxy Status Check
Check the health, configuration, and runtime status of the local LiteLLM proxy.
Steps
-
Check systemd service status
systemctl --user status litellm-proxyConfirm it shows
active (running). Note uptime, memory usage, and PID. -
Check health endpoint
curl -s http://127.0.0.1:4000/health | python3 -m json.toolVerify all models show as healthy with zero unhealthy endpoints.
-
List available models
curl -s http://127.0.0.1:4000/v1/models | python3 -m json.toolList all model IDs the proxy is serving.
-
Show configuration
cat ~/.config/litellm/config.yamlDisplay the current model list, project, location, and settings.
-
Show service configuration
cat ~/.config/systemd/user/litellm-proxy.serviceDisplay the systemd unit including the credentials path and startup command.
-
Check recent logs (only if there are issues)
journalctl --user -u litellm-proxy --no-pager -n 20
Report Format
Present a summary table:
| Item | Status |
|---|---|
| Service | active/inactive, uptime |
| Health | healthy/unhealthy endpoint count |
| Models | list of model names |
| Port | 4000 |
| Credentials | service account email from key file |
| Config | ~/.config/litellm/config.yaml |
Troubleshooting
If the service is not running:
systemctl --user start litellm-proxy
If the service fails to start, check logs:
journalctl --user -u litellm-proxy --no-pager -n 50
Changelog
See CHANGELOG.md for version history.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 82 lines · 22 tokens per session scan C a34e17dd6c81
litellm-proxy-status is a skill published in the GitHub repository rhtevan/agentfs (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 22 tokens to every session and 539 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…