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/KhaledSaeed18/dotclaudeWrote 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/commands/khaledsaeed18/dotclaude/prime)<a href="https://agentmods.dev/commands/khaledsaeed18/dotclaude/prime"><img src="https://agentmods.dev/badge/commands/khaledsaeed18/dotclaude/prime/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/commands/khaledsaeed18/dotclaude/prime"><img src="https://agentmods.dev/badge/commands/khaledsaeed18/dotclaude/prime.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.00063 | $0.00694 |
| Opus 5.5 | $0.00025 | $0.00278 |
| Sonnet 5.5 | $0.00013 | $0.00139 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
prime 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
Scope (optional): $ARGUMENTS
Project manifest:
!cat package.json 2>/dev/null || cat pyproject.toml 2>/dev/null || cat Cargo.toml 2>/dev/null || cat go.mod 2>/dev/null || echo "(no manifest found)"
Directory structure (top two levels):
!find . -maxdepth 2 -not -path '*/.git/*' -not -path '*/node_modules/*' -not -path '*/__pycache__/*' -not -path '*/dist/*' -not -path '*/.next/*' | sort | head -60
Recent commits:
!git log --oneline -15 2>/dev/null || echo "(not a git repository)"
Active branch and status:
!git status --short 2>/dev/null | head -20
Task
Read the files above and any additional ones needed to build a working mental model of this project. Then deliver a concise session brief.
Step 1: Extend the read
Beyond what is already injected above, read:
CLAUDE.mdorCLAUDE.local.mdif present (project-specific conventions for this session)README.mdorREADME(project purpose and setup)- The main entry point for the project (the
mainorindexfile, the root route file, or the top-levelsrc/directory) - Any architecture decision records (
docs/adr/,decisions/, or similar) if the scope argument names an area that would benefit from them
If $ARGUMENTS is set, focus the read on that path or module rather than the full project.
Step 2: Identify what matters right now
From the git log and status:
- What work is in progress (uncommitted or staged changes)?
- What was the last significant change (most recent meaningful commit)?
- Are there any open merge conflicts or rebase states?
Step 3: Deliver the session brief
Respond with four short sections, each under five lines:
Project: One sentence on what this project does and its primary tech stack.
Structure: The two or three most important directories and what lives in each. Skip boilerplate folders (node_modules, dist, .git).
Recent work: What the last few commits changed and whether any of that work is unfinished.
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 · 65 lines · 63 tokens per session scan A b2d079023d7f
prime is a command published in the GitHub repository KhaledSaeed18/dotclaude (5 stars, last pushed 3d ago), licensed MIT. It adds 63 tokens to every session and 694 once invoked, about $0.0003 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-31.
Other commands, from other repositories
AGENTS
The thirteen memory slash commands, registered once by the memory component through register.ts (registerMemoryCommands(pi, deps)). MEMORYCOMMANDNAMES: /memory /memfs /remember /init /doctor /recompile /memory-repository /sleeptime /reflect /dream /search /people /facts. Score 24 (53 files, DI surface, central…
learn
Extract patterns and learnings from current session.
export-closedloop-learnings
Exports pending ClosedLoop learnings to global location with deduplication.
memory-forget
Command "memory-forget" from waittim/MemoryCustodian, covering memory-forget and review the preview, then apply its plan id.
doctor
Diagnose the Remember plugin — resolved paths, detected tools, storage mode, and whether capture is actually saving memory.
check
Run a quick scan of the memory system's health. For daily use.