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 skills add boshu2/agentops --skill memorygit clone --depth 1 https://github.com/boshu2/agentopsWrote 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/skills/boshu2/agentops/memory)<a href="https://agentmods.dev/skills/boshu2/agentops/memory"><img src="https://agentmods.dev/badge/skills/boshu2/agentops/memory/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/skills/boshu2/agentops/memory"><img src="https://agentmods.dev/badge/skills/boshu2/agentops/memory.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.00051 | $0.01013 |
| Opus 5 | $0.00026 | $0.00507 |
| Sonnet 5 | $0.00010 | $0.00203 |
| Haiku 4.5 | $0.00005 | $0.00101 |
Grade A, and why
memory 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory
Use maintained experience only when it helps an actual task. Memory is optional: no mandatory recall at RPI entry, lesson at completion, worksheet, page quota or background mining. A trivial edit can proceed directly to implementation.
Choose one operation
| Need | Read on demand |
|---|---|
| An earlier constraint may change the next action | Recall |
| Learn from a bounded set of episodes, failures or corrections | Mine / learn |
| Update, qualify, consolidate or retire a supported claim | Curate / qualify / retire |
learn remains a compatible optional entrypoint for the mine/learn operation.
Specialist miners and operationalization tools are optional, never hard edges.
Do not load all operation references just because Memory was selected.
One authority per fact
BD or the caller's tracker owns work/status/dependencies/handoffs; Git owns content and delivery history; native sessions and CASS own episode evidence. The caller-selected reviewed external Markdown topic pages hold reusable claims, not another work account. Search and update an existing topic page before making a new one. Do not make one lesson file per session, copy a transcript lake, or silently initialize a memory store. Source evidence is not policy.
A useful entry states applicability, action, support, limits and invalidation: when it applies, what to do, the evidence, where it may fail, and what would change or retire it. One incident supports a narrow observation, not a universal rule. Stronger general rules need stronger independent/repeated evidence and later reapplication. Keep rare useful constraints; age or low frequency alone is no reason to delete them. Learning may simplify or remove rules.
Access, storage and honest limits
Use only sources already authorized for the task, owner, model/provider and
exact destination. Read permission does not imply publication or Git storage.
This lean path supports public or already-cleared trial inputs only. Native
restricted-source enforcement is not implemented by this skill, a prompt, a
worktree or a same-user shell; do not retrieve restricted material through this
path. The existing ao session read-source supported profile does not grant
broader access or automatic transcript access. Unavailable and denied evidence
remain explicit gaps; do not fetch then redact.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 100 lines · 51 tokens per session scan A 04bab7eb12ec
memory is a skill published in the GitHub repository boshu2/agentops (434 stars, last pushed today), licensed Apache-2.0. It adds 51 tokens to every session and 1,013 once invoked, about $0.0003 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-09-09.
Other skills, from other repositories
autolearn
Use when a verified non-trivial fix lands or existing solution docs need refresh. Not for unverified fixes.
consolidate-to-one-home
Fold a scattered fact into a single home and point the rest at it. Use when the same rule, constant, or definition is restated in several files, or the user says "consolidate this", "make this the single source of truth", or "ssotize this". The consolidation is proposed and approved before any edit lands. To…
cdb-scan
Map this codebase into project memory — a code graph of every symbol and how they connect, plus a written profile of stack, layout, conventions and workflows. Re-run any time to refresh both in place. Use when memory is newly installed on an existing project, or when the project has changed enough that the stored map…
ctx-purge
Purge the context-mode knowledge base. Permanently deletes all indexed content and resets session stats. This is destructive and cannot be undone. Trigger: /context-mode:ctx-purge.
ctx-search
Search context-mode's persistent FTS5 knowledge base for previously indexed local project content, documentation, or session memory. Trigger: /context-mode:ctx-search.
audit-project
Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".