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/bushans/okfgenWrote 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/bushans/okfgen/okfgen)<a href="https://agentmods.dev/mcp/bushans/okfgen/okfgen"><img src="https://agentmods.dev/badge/mcp/bushans/okfgen/okfgen/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/mcp/bushans/okfgen/okfgen"><img src="https://agentmods.dev/badge/mcp/bushans/okfgen/okfgen.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
okfgen 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 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.
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
{ "okfgen": { "command": "uvx", "args": [ "okfgen" ] } }
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 · 8 lines scan A 0d58cb12bbbc
okfgen is an MCP server published in the GitHub repository bushans/okfgen (0 stars, last pushed 14d 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
vectorlane
Open-source local vector memory engine for AI agents — ingest documents, chunk content, generate embeddings, search locally, return metadata/citations. Runs locally from the @talocode/vectorlane npm package.
data-workers
Data Workers CLI — autonomous AI agent swarm for data engineering. Runs locally from the dw-claw npm package.
mikro
MCP server "mikro" as configured in automagik-dev/genie. Launched with mikro mcp --dir ${CLAUDE_PROJECT_DIR}.
bigquery
A CLI tool for running a toolbox server. Runs locally from the @toolbox-sdk/server npm package.
atomicmemory
MCP server "atomicmemory" as configured in atomicstrata/atomicmemory. Runs locally from the atomicmemory-mcp npm package. Needs 7 environment variables to run.
neuronscope
CLI and MCP server for tracing which neurons and attention heads drive a language model's output, built on TransformerLens. Runs locally from the neuronscope-cli Python package.