SkillFM LLM Cost Optimizer
LLM cost optimizer for OpenAI, Anthropic, token usage, BYOK, and SkillFM Beacon audits.
Open source Open in the app JSON README (API)
About
LLM cost optimizer for OpenAI, Anthropic, token usage, BYOK, and SkillFM Beacon audits.
Details
- Kind
- MCP servers
- Topic
- AI, RAG & memory
- Publisher
- ericm1018
- Origin
- official
- Category
- ferramentas
- Transport
- local
- Version
- 0.1.0
- Last push
- 2026-05-20T13:57:24Z
- Repository state
- ativo
- Language
- JavaScript
- License
- MIT
- Added
- 2026-08-29 03:02:46
- Updated
- 2026-08-29 03:02:46
- Origin id
io.github.ericm1018/skillfm-llm-cost-optimizer-openai-anthropic-usage
README
# SkillFM LLM Cost Optimizer MCP
**LLM cost optimization and provider usage visibility for MCP-capable agents.**
This repository is a transparent SkillFM gateway package. It exists to match a specific marketplace/search intent, then delegates execution to the canonical [SkillFM Beacon MCP](https://www.npmjs.com/package/@skillfm/mcp) and local runtime.
Powered by SkillFM Beacon.
## Quick Start
Use this gateway as an MCP stdio server:
```bash
npx -y @skillfm/llm-cost-optimizer-mcp@latest
```
Equivalent explicit SkillFM entrypoint:
```bash
npx -y @skillfm/mcp@latest
```
For MCP clients that accept JSON config:
```json
{
"mcpServers": {
"llm-cost-optimizer": {
"command": "npx",
"args": ["-y", "@skillfm/llm-cost-optimizer-mcp@latest"]
}
}
}
```
## What This Gateway Helps With
- Turn LLM spend questions into SkillFM Beacon usage and health checks.
- Guide users from rough token visibility to provider-level BYOK monitoring when they are ready.
- Surface cost-saving opportunities in context, model choice, cache use, batching, and repeated work.
- Keep the public package thin while delegating execution to the SkillFM local runtime.
This gateway is for users who ask:
- "How do I reduce OpenAI or Anthropic spend?"
- "Which agent workflow is burning tokens?"
- "Can I optimize LLM cost without sending keys to a SaaS dashboard?"
- "How do I connect provider usage after I trust the local checkup?"
## How It Works
The public package is intentionally thin. It sets `SKILLFM_GATEWAY_SOURCE=llm-cost-optimizer` and forwards execution to `@skillfm/mcp@latest`, which then delegates to the canonical `@skillfm/local` runtime.
No private SkillFM platform logic, customer data, provider credentials, or backend modules live in this repository.
## Activation Path
Start the local sidecar when the user wants to connect SkillFM:
```bash
npx -y @skillfm/llm-cost-optimizer-mcp@latest start
```
Agent-driven activation flow:
1. Read the sidecar URL from stdout or `~/.skillfm/local.json`.
2. Call `POST <sidecar_url>/activate/start`.
3. Show the returned verification URL and real device code to the user.
4. Poll `POST <sidecar_url>/activate/poll` until it returns `activated: true`.
5. Use SkillFM Beacon MCP tools for checkups, usage visibility, BYOK guidance, and cleanup audits.
Do not fabricate a placeholder code. The device code must come from `POST /activate/start`.
## Security Model
- **Transparent gateway**: This package is a public search/distribution gateway, not a separate hidden product.
- **Local-first runtime**: Runtime execution goes through SkillFM's local package.
- **BYOK boundary**: Provider keys are introduced only after user value is established, and key values are not read back by agents.
- **No private core**: This repository contains distribution metadata, docs, and a thin launcher only.
- **Read-only first**: Cleanup and usage inspection begin with read-only audits.
See [PRIVACY.md](./PRIVACY.md) and [SECURITY.md](./SECURITY.md).
## Marketplace Keywords
LLM cost optimizer, OpenAI usage, Anthropic usage, token usage, AI cost optimizer, BYOK, SkillFM Beacon, MCP server.
Expected Official MCP Registry single-token hits:
- `llm-cost`
- `cost`
- `optimizer`
- `openai`
- `anthropic`
- `usage`
- `skillfm`
## License
MIT