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/agent-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/agent-memory-kit/executor)<a href="https://agentmods.dev/agents/awrshift/agent-memory-kit/executor"><img src="https://agentmods.dev/badge/agents/awrshift/agent-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/agent-memory-kit/executor"><img src="https://agentmods.dev/badge/agents/awrshift/agent-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.00207 | $0.00870 |
| Opus 5.5 | $0.00083 | $0.00348 |
| Sonnet 5.5 | $0.00041 | $0.00174 |
| Haiku 4.5 | $0.00021 | $0.00087 |
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 26d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- executor — 100% identical, 24 lines differ
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. - The input-coverage gate, BEFORE the first file: enumerate every value your slice must
produce, compute or display (from the spec's Acceptance and design); check each against the
spec's Value sources; any value with no named source is an OWED DECISION. Do not judge this
by feeling — the list is the test. On any gap: STOP, do not build, report the gap in the
fixed shape:
OWED DECISION · value: … · needed by: AC-n · candidates: …. You resume only when the integrator either amends the spec or answers "build anyway, assume X"; in the second case you first writeprojects/<name>/plans/YYYY-MM-DD-<slug>-assumed.mdfrom the kit'sASSUMED-SPEC-TEMPLATE.md(the ONLY spec file an executor may create), then build against it. You never edit an existing spec. - 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; the*-assumed.mdof rule 3 is the single exception. - 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.
- 26d ago Changed · +12 lines · +39 tokens per session 55a9d1477a59
- 1mo ago First seen · 40 lines · 168 tokens per session scan A 8587eec988ad
executor is an agent published in the GitHub repository awrshift/agent-memory-kit (34 stars, last pushed 8d ago), licensed MIT. It adds 207 tokens to every session and 870 once invoked, about $0.0008 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 agents, from other repositories
navigator-research
Specialized codebase exploration and architecture discovery. Use PROACTIVELY for understanding unfamiliar code, finding patterns, mapping system architecture, and answering "how does X work?" questions. Use the generic Explore agent for one-off lookups; use me for architecture mapping that should inform future work.…
deep-research-writer
Writes the single report.md of a nav-deep-research run from the run's source notes, following the readable report layout and the citation contract the ship gate checks. Spawned once by the nav-deep-research skill at step 3 (draft). Writes the report exactly once; later changes are the patcher's.
deep-research-critic
Adversarial reader of a nav-deep-research draft. Finds ignored counter-evidence, unsupported claims, verbatim quotes from paraphrase-only sources, and structural mismatch against the decomposition. Writes a findings JSON the patcher applies; cannot edit the report. Spawned once at step 4 by the nav-deep-research skill.
task-planner
Implementation planning and task breakdown specialist. Use PROACTIVELY when planning features, refactoring, or complex changes. Creates detailed implementation plans with effort estimates.
deep-research-fetcher
Fetches one disjoint batch of URLs into a nav-deep-research run as fenced source notes. Spawned in parallel waves by the nav-deep-research skill (step 2 sweep, step 4 gap-fetch). Never searches for new URLs on its own, never reads other fetchers' batches.
memcp-analyzer
Analyze a MemCP context using the RLM peek-identify-load-analyze pattern. Use proactively when answering questions about stored content without loading it all into the main context.