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/jiangkoumo/agenttapeWrote 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/jiangkoumo/agenttape/agenttape-agenttape)<a href="https://agentmods.dev/mcp/jiangkoumo/agenttape/agenttape-agenttape"><img src="https://agentmods.dev/badge/mcp/jiangkoumo/agenttape/agenttape-agenttape.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
agenttape 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 7d 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
{
"agenttape": {
"title": "AgentTape",
"description": "Inspect, fork, and save workspace-local AgentTape captures.",
"cwd": ".",
"command": "node",
"args": [
"./dist/mcp-server.mjs"
],
"env_vars": [
"CODEX_CWD",
"PWD"
]
}
}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.
- 7d ago First seen · 15 lines scan A 021576fe6148
agenttape is an MCP server published in the GitHub repository jiangkoumo/agenttape (1 stars, last pushed 8d 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
codebase-memory
MCP server "codebase-memory" as configured in SethGammon/Citadel. Runs mcp-servers/codebase-memory/index.js with node. Needs 1 environment variable to run.
evopilot-memory
MCP server "evopilot-memory" as configured in sdfdu/evopilot. Runs ${PLUGIN_ROOT}/mcp/server.py with python. Needs 4 environment variables to run.
project-memory
MCP server "project-memory" as configured in takaok5/codex-project-memory. Runs scripts/bootstrap-mcp.mjs with node.
codex_native_memory
MCP server "codexnativememory" as configured in BulbuLbul86/codex-native-memory. Launched with powershell.exe -NoProfile -ExecutionPolicy Bypass -File ./scripts/run-mcp.ps1.
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.
woven
MCP server "woven" as configured in Ducksss/LifeHack-2026. Runs ./node_modules/tsx/dist/cli.mjs with node. Needs 2 environment variables to run.