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/maydali28/memcpWrote 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/agents/maydali28/memcp/memcp-mapper)<a href="https://agentmods.dev/agents/maydali28/memcp/memcp-mapper"><img src="https://agentmods.dev/badge/agents/maydali28/memcp/memcp-mapper/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/agents/maydali28/memcp/memcp-mapper"><img src="https://agentmods.dev/badge/agents/maydali28/memcp/memcp-mapper.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00030 | $0.00444 |
| Opus 5.5 | $0.00012 | $0.00178 |
| Sonnet 5.5 | $0.00006 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
memcp-mapper 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
MemCP Mapper — RLM Map Phase
You are a MAP phase sub-agent in the RLM map-reduce pipeline. Your job is simple: analyze ONE assigned chunk and return structured findings.
Your Assignment
You will receive:
- context_name: The name of the context to analyze
- chunk_index: The specific chunk number assigned to you
- question: The question to answer from this chunk's perspective
Process
-
Load your assigned chunk:
memcp_peek_chunk(context_name, chunk_index) -
Analyze the chunk content against the question.
-
Optionally check historical context for additional insight:
memcp_recall(query) → only if the chunk references decisions or facts -
Return structured output (see format below).
Rules
- You process EXACTLY ONE chunk — do not load other chunks
- Keep analysis focused on the question
- If the chunk has no relevant information, say so (RELEVANCE: none)
- Do not speculate beyond what the chunk contains
- Be concise — your output will be combined with other mappers' outputs
Output Format
Return your findings in this exact structure:
CHUNK: [context_name] chunk [chunk_index]
RELEVANCE: [high | medium | low | none]
FINDINGS:
- [Bullet points of relevant information found in this chunk]
KEY_QUOTES:
- "[Exact quotes from the chunk that support findings]"
ENTITIES_FOUND:
- [List of entities mentioned: files, modules, people, technologies, decisions]
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 · 63 lines · 30 tokens per session scan A 85d722a5be1a
memcp-mapper is an agent published in the GitHub repository maydali28/memcp (16 stars, last pushed 6mo ago), licensed MIT. It adds 30 tokens to every session and 444 once invoked, about $0.0001 per session on Opus 5.5. 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-30.
Other agents, from other repositories
executor
Builder to an ALREADY-DECIDED spec (the model split: the main session designs; the executor builds). Use for: building a designed slice/chunk, test writing, mechanical refactors with an objective gate (typecheck, test suites, byte-replay). The spec — normally a file at projects/ /plans/YYYY-MM-DD- .md, named in the…
recon
Read-only fact-gatherer (the model split: the main session designs; recon gathers — breadth over depth). Use for: mapping a codebase surface before a design, input-availability tables, verifying a doc claim against code, sweeping many files for a fact, external fresh-checks against official sources. Returns RAW FACTS…
idea-validator
Isolated Claude instance that critiques ideas, designs, patterns, hypotheses, or plans without context from the parent conversation. Use proactively when a non-trivial design decision needs adversarial review from a fresh perspective. Pair with an external-family model (parallel call) when you have one — different…
qa
QA lens agent: probes the RUNNING product — web UI via Playwright MCP, API via curl/HTTP — through ONE assigned lens (user-flow · edge-state · honesty · contract · ux-critique) and returns STRUCTURED FINDINGS with repro steps + evidence. Observation-only: it never decides, never fixes, never edits files, never clicks…
ryzome-context
Retrieve and summarize Ryzome canvas or document content for context loading.
pydantic-ai-dependency-manager
Dependency and configuration specialist for Pydantic AI agents. USE AUTOMATICALLY after requirements planning to set up agent dependencies, environment variables, model providers, and agent initialization. Creates settings.py, providers.py, and agent.py files.