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.
git clone --depth 1 https://github.com/sachinuppal/modelcostsaverWrote 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/mcp/sachinuppal/modelcostsaver/modelcostsaver)<a href="https://agentmods.dev/mcp/sachinuppal/modelcostsaver/modelcostsaver"><img src="https://agentmods.dev/badge/mcp/sachinuppal/modelcostsaver/modelcostsaver.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
modelcostsaver scanned grade A with 0 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 8d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"modelcostsaver": {
"command": "npx",
"args": [
"-y",
"@workswarm/modelcostsaver"
],
"env": {}
}
}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.
- 8d ago First seen · 10 lines scan A 2eabf0ad1c61
modelcostsaver is an MCP server published in the GitHub repository sachinuppal/modelcostsaver (0 stars, last pushed 2mo ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
llm-sidecar
Local sidecar giving any tool grounded, cited, routed AI — Ollama or OpenRouter, no API key required. Runs locally from the llm-sidecar Python package.
promptthrift-mcp
MCP server "promptthrift-mcp" as configured in woling-dev/promptthrift-mcp. Runs locally from the promptthrift-mcp Python package.
openrouter-multimodal
Chat with 300+ LLMs via OpenRouter. Analyze and generate images, audio, and video from MCP. Runs locally from the @stabgan/openrouter-mcp-multimodal npm package. Needs 13 environment variables to run.
mistral
MCP server exposing Mistral AI capabilities over MCP: chat, embeddings, FIM, vision, OCR, audio, agents, moderation, classification, files, batch, workflows, sampling, prompts, resources, and Streamable HTTP. Runs locally from the mistral-mcp npm package. Needs 1 environment variable to run.
mistral-mcp
Mistral AI MCP server: chat, OCR, Voxtral audio, Codestral FIM, vision, agents, batch. Runs locally from the mistral-mcp npm package. Needs 1 environment variable to run.
local-delegate
Delegate mechanical text tasks to a local OpenAI-compatible LLM endpoint to conserve Claude subscription quota. Runs locally from the local-delegate-mcp Python package. Needs 2 environment variables to run.