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/paulbreuler/limps/002-agent-memorygit clone --depth 1 https://github.com/paulbreuler/limpsWhat 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.00000 | $0.00576 |
| Opus 5 | $0.00000 | $0.00288 |
| Sonnet 5 | $0.00000 | $0.00115 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
002-agent-memory 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 2d 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
Agent 002: Agent Memory System
Objective
Implement persistent memory for agents that survives across sessions.
Tasks
-
Memory types (
src/memory/types.ts)Finding: Discoveries during workDecision: Choices with rationaleBlocker: Open or resolved blockersSessionLog: Brief session notes
-
Memory manager (
src/memory/agent-memory.ts)getMemory(planId, agentId): Load memory fileaddFinding(planId, agentId, text): Add findingaddDecision(planId, agentId, choice, rationale): Add decisionaddBlocker(planId, agentId, issue, status): Add blockerlogSession(planId, agentId, notes): Add session entry- Auto-create memory file if missing
-
Memory CLI (
src/cli/commands/memory/)limps memory show <plan> <agent>— Display memorylimps memory add <plan> <agent> finding <text>limps memory add <plan> <agent> decision <choice> --rationale <why>limps memory add <plan> <agent> blocker <issue> --status open|resolvedlimps memory session <plan> <agent> <notes>limps memory clear <plan> <agent>— Reset with confirmation
Memory File Format
---
agent: 001-entity-resolution
plan: 0042-knowledge-graph
created: 2026-02-01
updated: 2026-02-02
sessions: 3
---
# Agent Memory: Entity Resolution
## Findings
- Finding 1...
- Finding 2...
## Decisions
| Decision | Choice | Rationale | Date |
|----------|--------|-----------|------|
## Blockers
- [ ] Open blocker
- [x] ~~Resolved blocker~~
## Session Log
### Session N — Date
Notes...
Acceptance Criteria
- Memory persists in
{agent}.memory.mdfile -
limps memory showdisplays formatted memory -
limps memory addappends to correct section - Session count increments automatically
- Memory files are human-readable markdown
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.
- 2d ago First seen · 80 lines · 0 tokens per session scan A 1558ea73a3bb
002-agent-memory is an agent published in the GitHub repository paulbreuler/limps (10 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 576 tokens. 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
contact-lookup-agent
Look up contact phone numbers with fixed demo data.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
nodejs-expert
Specializes in Node.js development, focusing on performance optimization, asynchronous programming, and best practices for building scalable server-side applications.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
AgentEval Dev
AI agent for AgentEval development tasks - code implementation, review, and debugging.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.