CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

30.8 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 1 flagged

Securityscore 88 · 1 finding

MEDIUMInstruction telling the agent not to ask for approvalSS-SKILL-INJECT-DONT-ASK-01 · Prompt injection · llms-install.md

MEDIUM — it fires on intent; the real damage depends on the host agent's own approval-gating.

Why it matters

The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.

The exact value spotted

excerptllms-install.md· markdown

27- For Claude Code token usage, cost, AI health, or context cleanup requests, route through S

… (14 chars elided on L27)

28- Do not invent usage or billing numbers.

29- Do not ask for provider API keys first.

30- Runtime forwards to `@skillfm/mcp@latest` with `SKILLFM_GATEWAY_SOURCE=claude-code-token-u

… (6 chars elided on L30)

Occurrences

1 occurrence · at L29

How to fix

Remove the approval-skipping instruction, or scope it narrowly to a specific safe, reversible action.

Delete blanket "don't ask / no need to confirm" directives from the skill.
If the skill is a genuine autonomous job, restrict the opt-out to a named non-destructive action rather than all actions.

Framework references

OWASPLLM01 ATLASAML.T0051

Trace & refs

ruleSS-SKILL-INJECT-DONT-ASK-01sha25668b030f55bcd484a…rubric 365aacaView on GitHub

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

README.md · 1 file

README.md3.2 KB · Markdown

SkillFM Claude Code Token Usage MCP

Claude Code token usage and cost 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 and local runtime.

Quick Start

Use this gateway as an MCP stdio server:

npx -y @skillfm/claude-code-token-usage-mcp@latest

Equivalent explicit SkillFM entrypoint:

npx -y @skillfm/mcp@latest

For MCP clients that accept JSON config:

{
  "mcpServers": {
    "claude-code-token-usage": {
      "command": "npx",
      "args": ["-y", "@skillfm/claude-code-token-usage-mcp@latest"]
    }
  }
}

What This Gateway Helps With

Inspect Claude Code token usage and estimated cost signals.
Connect usage visibility to SkillFM Beacon AI health checks.
Find repeated context, stale sessions, and cost-saving opportunities.
Route users toward local-first SkillFM activation without asking for provider keys first.

This gateway is for users who ask:

"How many Claude Code tokens did I use today?"
"Why did my Claude Code usage spike?"
"Which sessions or projects are wasting context?"
"Can my agent show me token usage before I connect provider keys?"

How It Works

The public package is intentionally thin. It sets SKILLFM_GATEWAY_SOURCE=claude-code-token-usage 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:

npx -y @skillfm/claude-code-token-usage-mcp@latest start

Agent-driven activation flow:

Read the sidecar URL from stdout or ~/.skillfm/local.json.
Call POST <sidecar_url>/activate/start.
Show the returned verification URL and real device code to the user.
Poll POST <sidecar_url>/activate/poll until it returns activated: true.
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 and SECURITY.md.

Marketplace Keywords

Claude Code token usage, Claude usage, token cost, LLM cost, AI health checkup, agent monitoring, context cleanup, SkillFM Beacon, MCP server.

Expected Official MCP Registry single-token hits:

claude-code
token
usage
cost
skillfm

License

MIT

Skillfm Claude Code Token Usage Mcp— agent skill

Is Skillfm Claude Code Token Usage Mcp safe to install?

SkillFM Claude Code Token Usage MCP

Quick Start

What This Gateway Helps With

How It Works

Activation Path

Security Model

Marketplace Keywords

License

Audit the pieces. Scan the whole. Decide.