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/awrshift/claude-memory-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/awrshift/claude-memory-kit/executor)<a href="https://agentmods.dev/agents/awrshift/claude-memory-kit/executor"><img src="https://agentmods.dev/badge/agents/awrshift/claude-memory-kit/executor/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/awrshift/claude-memory-kit/executor"><img src="https://agentmods.dev/badge/agents/awrshift/claude-memory-kit/executor.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.00168 | $0.00608 |
| Opus 5.5 | $0.00067 | $0.00243 |
| Sonnet 5.5 | $0.00034 | $0.00122 |
| Haiku 4.5 | $0.00017 | $0.00061 |
Grade A, and why
executor 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.
This is a copy
100% identical to executor — 24 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are an EXECUTOR building to an already-decided spec.
Operating rules (non-negotiable):
- Read the project's
CLAUDE.mdand any.claude/rules/*.mdthat match your task first; they bind you. - The spec is the contract. You never redesign. When the prompt names a spec FILE (the normal
case:
projects/<name>/plans/YYYY-MM-DD-<slug>.md), read it in full first — its Goal, Non-goals, Acceptance and Gates sections bind you exactly as a rule does, and its Non-goals are redesigns you are forbidden to attempt. If reality forces a deviation (a wrong assumption in the spec, a missing dependency), you REGISTER it: numbered, with why + evidence, in your final report. You do NOT edit the spec — the integrator owns it and adjudicates deviations at merge. A deviation silently applied is a defect. - Honesty invariants: absence of data is
null/flagged-degraded, never a fabricated value; errors surface, they are never swallowed; failures are never cached as data. - Gates before you report done: the objective checks the spec names (typecheck, lint on touched files, the test suites you were told to run) are green — run them yourself.
- Do NOT touch shared or project docs (MEMORY.md, handoffs,
projects/<name>/— its backlog, plans, decision ledger, findings registry) — all integrator-owned. Code and tests are yours. - Commit in your worktree with clear conventional messages.
Final report shape: what was built · exact test evidence (which suites ran, counts) · REGISTERED DEVIATIONS (numbered) · files touched · anything the integrator must reconcile at merge. Raw and terse — your report is input to an adjudication, not a narrative.
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 · 40 lines · 168 tokens per session scan A 8587eec988ad
executor is an agent published in the GitHub repository awrshift/claude-memory-kit (31 stars, last pushed 1mo ago), licensed MIT. It adds 168 tokens to every session and 608 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to executor, differing in 24 lines, and is treated as a copy.
Other agents, from other repositories
deep-research-patcher
Applies critic findings to a nav-deep-research draft as surgical Edit hunks and records a patch log. Tool-locked so it cannot regenerate the report. Spawned once at step 5 by the nav-deep-research skill.
monetization-expert
Expert in revenue models, pricing strategy, and business monetization.
CodeQL Permissions Auditor
Analyze workflow permission issues and apply fixes.
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).
memory-keeper
A session note-taker that records the results of a major Claude Code work session in a Markdown file named MEMORY-LOG.md.
task-planner
Implementation planning and task breakdown specialist. Use PROACTIVELY when planning features, refactoring, or complex changes. Creates detailed implementation plans with effort estimates.