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/heyayushh/stacc/agents-memory-updatergit clone --depth 1 https://github.com/heyAyushh/staccWrote 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/heyayushh/stacc/agents-memory-updater)<a href="https://agentmods.dev/agents/heyayushh/stacc/agents-memory-updater"><img src="https://agentmods.dev/badge/agents/heyayushh/stacc/agents-memory-updater.svg" alt="Measured on agentmods" 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.00028 | $0.00405 |
| Opus 5 | $0.00014 | $0.00202 |
| Sonnet 5 | $0.00006 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
agents-memory-updater 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 5d 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.
What it actually says
AGENTS.md memory updater
Own the full memory update flow for continual learning.
Trigger
Use from continual-learning when transcript deltas may produce durable memory updates.
Workflow
- Read existing
AGENTS.mdfirst. If it does not exist, create it with only:## Learned User Preferences## Learned Workspace Facts
- Load the incremental index if present.
- Inspect only transcript files under
~/.cursor/projects/<workspace-slug>/agent-transcripts/that are new or have newer mtimes than the index. - Pull out only durable, reusable items:
- recurring user preferences or corrections
- stable workspace facts
- Update
AGENTS.mdcarefully:- update matching bullets in place
- add only net-new bullets
- deduplicate semantically similar bullets
- keep each learned section to at most 12 bullets
- Refresh the incremental index for processed transcripts and remove entries for files that no longer exist.
- If the merge produces no
AGENTS.mdchanges, leaveAGENTS.mdunchanged but still refresh the index. - If no meaningful updates exist, respond exactly:
No high-signal memory updates.
Guardrails
- Use plain bullet points only.
- Keep only these sections:
## Learned User Preferences## Learned Workspace Facts
- Do not write evidence/confidence tags.
- Do not write process instructions, rationale, or metadata blocks.
- Exclude secrets, private data, one-off instructions, and transient details.
Output
- Updated
AGENTS.mdand.cursor/hooks/state/continual-learning-index.jsonwhen needed - Otherwise exactly
No high-signal memory updates.
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.
- 5d ago First seen · 48 lines · 28 tokens per session scan A 93dfb244f173
agents-memory-updater is an agent published in the GitHub repository heyAyushh/stacc (3 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 405 once invoked, about $0.0001 per session on Opus 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
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
adapter_grok
Grok is an eagerly registered stock-TUI adapter. RimZ launches grok, installs passive global hooks in ${GROKHOME:-/.grok}/hooks/rimz.json, and enriches each session from its durable updates.jsonl, summary.json, signals.json, and optional events.jsonl files. ACP and provider-private billing APIs stay outside this…
starlight-repos-extractor
Tier: Phase 1 extractor Dispatched via: Agent tool Output contract: JSONL atoms appended to.
portable-memory-parent-orchestrator
Top orchestrator for the portable-process-memory feature. Delegates to sync-transport (push/fetch folded into the verbs, plain-git, credential inheritance, offline-fail-safe) and event-fold (ownership events + the fail-closed divergence tripwire in the gate fold). Architect-only; coordinates portability/transport work…
context
Agent "context" from hannsxpeter/godpowers, covering scope, context, decisions, rules and workflows.