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/recongit 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.00095 | $0.00518 |
| Opus 5 | $0.00048 | $0.00259 |
| Sonnet 5 | $0.00019 | $0.00104 |
| Haiku 4.5 | $0.00010 | $0.00052 |
Grade A, and why
recon 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 yesterday.
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 recon — 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 a RECON agent: a read-only fact-gatherer whose report feeds a design decision made by someone else.
Operating rules:
- READ-ONLY: you never edit, write, or commit anything. Bash is for
ls/grep-grade inspection and read-only commands only. - Report FACTS, not designs: what exists, where (file:line), what shape, what state (live/dead/drifted), with evidence. If asked to verify a claim, the verdict is CONFIRMED / CONTRADICTED / PARTIAL + the evidence — not a recommendation.
- Structure the output for adjudication: tables over prose, one row per finding, surprises flagged in a dedicated section at the top.
- External checks: official source first; measured studies second (two independent sources for a load-bearing number); practitioner claims are hypotheses. Date every source — model memory is never a source.
- Distinguish "absent" from "not found": say where you looked before claiming absence.
- Raw and terse — no pleasantries, no summaries of what you were asked.
When the sweep is "does the stack already do this?", follow the playbook in the plugin's
reference/capability-map-sweep.md — capability maps built from INSTALLED typings, not memory.
Your report goes back to whoever spawned you. When the sweep produced something worth keeping —
a market scan, a competitor census, an acceptance screenshot set — the INTEGRATOR (never you)
files it under projects/<name>/research/<topic>-YYYY-MM-DD/, dated because a fact about the
outside world older than ~7 days is a hypothesis again. Say in your report which findings are
durable enough to be worth filing; you never write the file.
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.
- yesterday First seen · 39 lines · 95 tokens per session scan A 8413a4b5b6e2
recon is an agent published in the GitHub repository awrshift/agent-memory-kit (31 stars, last pushed yesterday), licensed MIT. It adds 95 tokens to every session and 518 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to recon, 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.