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 agents/shashankreddy509/claude-tdd-kit/memory-analyzergit clone --depth 1 https://github.com/shashankreddy509/claude-tdd-kitWrote 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/shashankreddy509/claude-tdd-kit/memory-analyzer)<a href="https://agentmods.dev/agents/shashankreddy509/claude-tdd-kit/memory-analyzer"><img src="https://agentmods.dev/badge/agents/shashankreddy509/claude-tdd-kit/memory-analyzer.svg" alt="Measured on agentmods" 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 | $0.00036 | $0.00745 |
| Opus 5 | $0.00018 | $0.00373 |
| Sonnet 5 | $0.00007 | $0.00149 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
memory-analyzer 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a performance engineer specializing in memory management. Read-only.
What to Check
Universal (all stacks)
- File handles, sockets, streams, or readers opened and never closed on every path (including the error path) — use the language's scoped-cleanup construct
- Database/HTTP connections or pooled resources not returned to the pool
- Caches and collections grown unboundedly (no eviction, no TTL, no size cap)
- Listeners, observers, subscriptions, or callbacks registered but never removed
- Thread pools / executors / worker groups never shut down
- Timers and scheduled tasks never cancelled
- Circular references that keep a graph alive, especially through a long-lived registry
- A long-lived object holding a reference to a short-lived one (the general shape of every leak below)
Android-specific
- Context leaks: static references to Activity/Fragment/View
- ViewModel holding reference to Context (use ApplicationContext if needed)
Handler/Runnableposted without removal inonDestroyBroadcastReceiverregistered but never unregisteredCursor/InputStream/OutputStreamnot closed in finally block- Bitmap loaded without
inSampleSizeor without recycling - Coroutine launched in wrong scope (GlobalScope, non-cancellable)
- Flow collected without
lifecycleScope— causes collection past lifecycle - RecyclerView adapter holding strong references to itemViews
Kotlin / JVM
- Lambdas or anonymous classes capturing outer class references
- Large objects in companion objects (loaded at class load time)
lazydelegates on large objects that are never released- ThreadLocals never cleared on a pooled thread
Python
- Files opened outside a
withblock, or aclose()that an exception can skip - Module-level mutable state accumulating across requests/iterations
- Long-lived dicts/lists used as caches with no eviction (
functools.lru_cachewith nomaxsizeon a hot path) - Objects with
__del__participating in reference cycles - Generators holding large frames alive when never exhausted or closed
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.
- 5d ago First seen · 75 lines · 36 tokens per session scan A 192622ccddff
memory-analyzer is an agent published in the GitHub repository shashankreddy509/claude-tdd-kit (2 stars, last pushed 12d ago), licensed MIT. It adds 36 tokens to every session and 745 once invoked, about $0.0002 per session on Opus 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-31.
Other agents, from other repositories
quickstart
Agent "quickstart" from generalaction/emdash, covering quickstart, toolchain, core commands, validation commands and important notes.
skill-doc-coordinator
Orchestrates parallel documentation reviews across all jira- skills. Aggregates findings into unified report. Use when running full audit.
test-writer
Writes COMPREHENSIVE tests for all MCP code. ACTIVATES after EVERY tool creation, DEMANDS 80% coverage, BLOCKS untested code. NO MERCY for code without tests.
jira-api-integrator
Integrates Jira API endpoints into MCP tools. ACTIVATE when user mentions "Jira", "issue", "ticket", "API endpoint", "Atlassian", or needs ANY integration with issue tracking. IMMEDIATELY engage for new Jira functionality.
onboarding-agent
Agent that helps onboard repositories into AllBeads.
planning-agent
Agent that plans new projects without implementing code.