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/CSOAI-ORG/filesystem-opsWrote 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/csoai-org/filesystem-ops/filesystem-ops)<a href="https://agentmods.dev/mcp/csoai-org/filesystem-ops/filesystem-ops"><img src="https://agentmods.dev/badge/mcp/csoai-org/filesystem-ops/filesystem-ops/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/csoai-org/filesystem-ops/filesystem-ops"><img src="https://agentmods.dev/badge/mcp/csoai-org/filesystem-ops/filesystem-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
filesystem-ops 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
{ "filesystem-ops": { "command": "npx", "args": [ "-y", "@meok-ai-labs/filesystem-ops" ] } }
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 · 9 lines scan A f67fcf23bd2f
filesystem-ops is an MCP server published in the GitHub repository CSOAI-ORG/filesystem-ops (0 stars, last pushed 11d ago), licensed MIT. 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
digital-human-library
MCP server "digital-human-library" as configured in CSOAI-ORG/digital-human-library. Runs locally from the @meok-global/digital-human-library npm package.
secure-comms
MCP server "secure-comms" as configured in CSOAI-ORG/secure-comms. Runs locally from the @meok-ai-labs/secure-comms npm package.
real-estate-ai
MCP server "real-estate-ai" as configured in CSOAI-ORG/real-estate-ai. Runs locally from the @meok-global/real-estate-ai npm package.
employment-ai
MCP server "employment-ai" as configured in CSOAI-ORG/employment-ai. Runs locally from the @meok-global/employment-ai npm package.
ai-economy-infrastructure
MCP server "ai-economy-infrastructure" as configured in CSOAI-ORG/ai-economy-infrastructure. Runs locally from the @meok-global/ai-economy-infrastructure npm package.
healthcare-ai
MCP server "healthcare-ai" as configured in CSOAI-ORG/healthcare-ai. Runs locally from the @meok-global/healthcare-ai npm package.