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/zhuangguangdahyh-dotcom/content-ops-studioWrote 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/zhuangguangdahyh-dotcom/content-ops-studio/content-ops-studio-content-ops)<a href="https://agentmods.dev/mcp/zhuangguangdahyh-dotcom/content-ops-studio/content-ops-studio-content-ops"><img src="https://agentmods.dev/badge/mcp/zhuangguangdahyh-dotcom/content-ops-studio/content-ops-studio-content-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/zhuangguangdahyh-dotcom/content-ops-studio/content-ops-studio-content-ops"><img src="https://agentmods.dev/badge/mcp/zhuangguangdahyh-dotcom/content-ops-studio/content-ops-studio-content-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
content-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 11d 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
{
"content-ops": {
"type": "stdio",
"command": "node",
"args": [
"${PLUGIN_ROOT}/runtime/dist/content-ops-mcp.mjs"
],
"cwd": "${PLUGIN_ROOT}",
"env": {
"CONTENT_OPS_HOME": "${PLUGIN_DATA}/content-ops-home",
"CONTENT_OPS_RUNTIME_MODE": "PRODUCTION",
"CONTENT_OPS_WORKSPACE_ADAPTER": "lark-cli",
"CONTENT_OPS_RENDERER": "playwright-html-css",
"CONTENT_OPS_PLAYWRIGHT_BROWSERS_PATH": "${PLUGIN_DATA}/playwright-browsers",
"PLAYWRIGHT_BROWSERS_PATH": "${PLUGIN_DATA}/playwright-browsers"
}
}
}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.
- 11d ago First seen · 18 lines scan A de0071b1ee8d
content-ops is an MCP server published in the GitHub repository zhuangguangdahyh-dotcom/content-ops-studio (0 stars, last pushed 15d 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
grok
MCP server "grok" as configured in stdevMac/grok-in-codex. Runs ./mcp/server.mjs with node.
mediamcp
Generate and edit images and video via OpenRouter or any OpenAI-compatible API. Runs locally from the mediamcp npm package. Needs 3 environment variables to run.
mcp-flux-pro
MCP Server for Flux AI Image Generation via AceDataCloud API. Runs locally from the mcp-flux-pro Python package. Needs 1 environment variable to run.
local-gpu-imagegen
MCP server "local-gpu-imagegen" as configured in ChevalGrand520/local-gpu-imagegen. Runs scripts/mcp_server.py with python.
image-video
Generate images, video & speech with Nano Banana, Veo, Omni and Gemini TTS. Pay as you go. Remote server at bananabanana.pro.
memory
Gives the agent a persistent knowledge graph it can write facts to and recall across sessions. Runs locally from the @modelcontextprotocol/server-memory npm package. Needs 1 environment variable to run.