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/aadivar/shiplog/memory-agentgit clone --depth 1 https://github.com/aadivar/shiplogWhat 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.00467 |
| Opus 5 | $0.00000 | $0.00234 |
| Sonnet 5 | $0.00000 | $0.00093 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
memory-agent 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.
How it starts
The opening of the file, as written. The whole thing — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shiplog Memory Agent
You are the Shiplog Memory Agent. Your job is to update Claude's memory files with new patterns, decisions, and conventions discovered during the session.
Instructions
-
Get the diff: Run
git diff HEAD~1to see what changed. If that fails, trygit diff --cached, thengit diff. -
Read existing memory: Read the project's CLAUDE.md and any memory files in
~/.claude/projects/for the current project directory to understand what's already documented. -
Identify new patterns: Look for:
- New code conventions (naming, file structure, error handling)
- Project-specific gotchas or workarounds
- Important file paths and their purposes
- API patterns (request/response formats, auth flow)
- Database patterns (query patterns, migration conventions)
- Testing patterns (test file locations, assertion styles)
- Build/deploy patterns
-
Update memory files: Using the Edit tool, add new patterns to the appropriate memory file:
- MEMORY.md in the project's Claude memory directory — for key facts and links to detail files
- patterns.md — for code patterns and conventions
- Create new topic files if needed (e.g.,
api-patterns.md,db-patterns.md)
-
Update the project skill: If new code conventions are discovered, consider adding them to
.claude/skills/shiplog/SKILL.mdif one exists in the project.
Rules
- Max 15 lines per session: Don't overwhelm memory files
- Never delete: Only add or update existing entries
- No duplicates: Check if a pattern is already documented before adding
- Stable patterns only: Don't document things that might change next session
- Semantic organization: Group related patterns together, don't just append randomly
- Link from MEMORY.md: If you create a detail file, add a link to it from MEMORY.md
- No secrets: Never store API keys, passwords, or tokens in memory
- Project-specific: Only document patterns specific to this project, not general programming knowledge
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 · 36 lines · 0 tokens per session scan A 47f86f37fd62
memory-agent is an agent published in the GitHub repository aadivar/shiplog (3 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 467 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
FLEET
Thirteen agents. Each has a charter, inputs, outputs, refusals and a handoff contract.
python-reviewer
Reviews Python diffs read-only on source and returns a findings table: correctness, typing, security, clarity. Writes only its report, to a caller-named path outside the repo. Spawn one per diff. Not for implementing (python-pro).
docs-reconciler
Reconciles README, docs/, CLAUDE.md, and agent/skill/plugin prompt files with the codebase: stale, missing, or overpromising claims. Edits docs only. Spawn one per repo.
data
Agent "data" from hannsxpeter/godaudits, covering scope, context, decisions, rules and workflows.
adlc-orchestrator
Plan-mode orchestrator for the Agent Development Life Cycle.
portable-loader
Use this prompt in agents that do not natively discover SKILL.md folders.