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.
npx agentmods add mcp/richawo/yaps-codex-plugin/yaps-memory-yapsgit clone --depth 1 https://github.com/richawo/yaps-codex-pluginWrote 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/richawo/yaps-codex-plugin/yaps-memory-yaps)<a href="https://agentmods.dev/mcp/richawo/yaps-codex-plugin/yaps-memory-yaps"><img src="https://agentmods.dev/badge/mcp/richawo/yaps-codex-plugin/yaps-memory-yaps.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
yaps 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 3d 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
{
"yaps": {
"command": "node",
"args": [
"./mcp/server/index.mjs"
],
"cwd": ".",
"env": {
"YAPS_MCP_CLIENT_ID": "codex",
"YAPS_MCP_AUTO_AUTHORIZE_READ": "1",
"YAPS_PLUGIN_ID": "yaps-memory",
"YAPS_PLUGIN_VERSION": "0.2.15",
"YAPS_PLUGIN_HOST": "codex_plugin",
"YAPS_PLUGIN_TRANSPORT": "mcp"
}
}
}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.
- 3d ago First seen · 17 lines scan A 0560284281c5
yaps is an MCP server published in the GitHub repository richawo/yaps-codex-plugin (2 stars, last pushed 5d 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
samong
MCP server "samong" as configured in waanvar/samong. Launched with https://github.com/waanvar/samong/releases/download/v0.4.1/samong-mcp.mcpb.
consilience
MCP server "consilience" as configured in Abner-Machado/consilience. Runs locally from the consilience Python package.
iwe
Markdown knowledge base as agent memory. Runs against the notes directory it is started in. Runs locally from the @iwe-org/mcp npm package.
openflowkit-mcp
Local-first OpenFlowKit diagramming tools for Claude, Cursor, Windsurf & other MCP clients. Runs locally from the @vrun-design/openflowkit-mcp npm package.
remnic
MCP server "remnic", hosted remotely at localhost, as configured in joshuaswarren/remnic.
rag-rat
CLI and MCP entrypoint for indexing repositories into local source, graph, history, and memory evidence. Runs locally from the @rag-rat/bin npm package.