forge-embeddings — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited forge-embeddings (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Forge is Voxell's hosted text-embedding API. This skill covers using it through the @voxell/forge-mcp server, which exposes two tools: `embed` (text → vectors) and `list_models`. Forge does embeddings only — it does not store text, search, or do RAG for you; you keep and query the vectors yourself.
The server runs over npx and needs one env var, FORGE_API_KEY (free key, 10M tokens, no card, at https://dash.voxell.ai). Standard MCP config:
{ "mcpServers": { "forge": { "command": "npx", "args": ["-y", "@voxell/forge-mcp"],
"env": { "FORGE_API_KEY": "your-key-here" } } } }Call list_models if unsure. Three tiers trade quality for size/cost:
| model | dim | when to use |
|---|---|---|
turbo | 1024 | default — fast, cheap, good for most search/RAG |
pro | 2560 | higher quality when turbo isn't separating results well |
ultra | 4096 | top quality — Qwen3-Embedding-8B (~75+ avg task score on MTEB, currently #4 on MTEB English; the models ranked above it are research-only, so it's the top usable one) |
Start with turbo; move up only if retrieval quality is the bottleneck. Higher dims cost more to store and compare.
embedArguments: input (string or string[]), model (default turbo), dim (optional, Matryoshka truncation), input_type ("query" or "document", default document).
Rules that matter for quality:
input_type: "document" and theuser's search text with input_type: "query". Mismatching them degrades retrieval.
dim below the model default (e.g. 256) for smaller, cheapervectors that stay re-normalized — trade a little accuracy for ~4× less storage. Use the same dim for documents and queries.
embed each document chunk with input_type:"document",store the vectors; at query time embed the query with input_type:"query" and rank stored vectors by cosine similarity. Forge returns the vectors — storage and the nearest-neighbor search are yours (a vector DB, numpy, etc.).
embed two (or many) texts, compare cosine similarity; highsimilarity ⇒ near-duplicate.
embed a batch, then cluster (k-means) or train a classifier on thevectors.
ultra "the best/top-ranked" embedding model — say "~75+ avg task score, #4 on MTEBEnglish, top usable model." Don't link a leaderboard.
turbo/pro — it's the ultra/8B model.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.