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/awrshift/agent-memory-kit/executorgit clone --depth 1 https://github.com/awrshift/agent-memory-kitWhat 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.00168 | $0.00608 |
| Opus 5 | $0.00084 | $0.00304 |
| Sonnet 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 today.
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 — 0 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.
- today First seen · 40 lines · 168 tokens per session scan A 8587eec988ad
executor is an agent published in the GitHub repository awrshift/agent-memory-kit (31 stars, last pushed yesterday), licensed MIT. It adds 168 tokens to every session and 608 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to executor, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
archivist
Processes document intake in batches — scans filesystem and mail sources, classifies documents against routing rules, previews moves, executes approved moves, and logs to the audit trail. Use for large file/mail archiving batches that would dump too many filenames into the main session context, or when the user says…
codebase-researcher
코드베이스 탐색, 기존 패턴 조사, 영향 범위 분석이 필요할 때 사용한다.
security-reviewer
인증, 권한, 결제, 데이터 삭제, 외부 입력 처리 변경 전후에 사용한다.
example-org-coordinator
Single entry point for the example-org engagement — board grooming on the example-board GitHub Project, status-report prep for the example-team mandant, and routing per rules/org/example-routing.md. Spawn for board sync, weekly status collection, or any example-org coordination that would dump too much raw output into…
code-analyst
Investigates code-level issues in the agency's Python stack (Django, FastAPI, SQLAlchemy) — debugging, log analysis, query optimization, test-coverage gaps. Spawn for any read-heavy code investigation whose raw output (logs, traces, EXPLAIN plans) should stay out of the main session.
ops-officer
Keeps the agency's multi-client task boards clean — GitHub Projects V2 sync, field updates, weekly client status prep, iteration planning. Spawn for board grooming or status-report collection across BigCorp, StartupXYZ, and internal work.