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 8Dionysus/aoa-skills --skill aoa-memo-writebackgit clone --depth 1 https://github.com/8Dionysus/aoa-skillsWrote 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/8dionysus/aoa-skills/aoa-memo-writeback)<a href="https://agentmods.dev/skills/8dionysus/aoa-skills/aoa-memo-writeback"><img src="https://agentmods.dev/badge/skills/8dionysus/aoa-skills/aoa-memo-writeback/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/8dionysus/aoa-skills/aoa-memo-writeback"><img src="https://agentmods.dev/badge/skills/8dionysus/aoa-skills/aoa-memo-writeback.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.00095 | $0.01672 |
| Opus 5.5 | $0.00038 | $0.00669 |
| Sonnet 5.5 | $0.00019 | $0.00334 |
| Haiku 4.5 | $0.00010 | $0.00167 |
Grade A, and why
aoa-memo-writeback 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aoa-memo-writeback
Intent
Preserve the first writeback judgment that the previous consolidation removed: notice when live or closing work produced a bounded lesson worth remembering, decide its real owner, and create or route its first guarded artifact without turning session history into memory truth.
Trigger boundary
Use this skill when:
- a live session, closeout, PR, diff, review, release, or recurring correction may contain a durable owner lesson not captured by the final artifact alone, and no concrete memo candidate, export, or memory object exists yet
- the decision is still whether to write a local candidate, prepare an export, record route-only debt, request owner review, or write nothing
- the caller explicitly authorizes creation of the first guarded local candidate from inspectable work evidence
Do not use this skill when:
- the task is eval-trigger/session-case mining,
.aoapreservation/index repair, generic session harvest, review of an existing candidate/export/ quarantine packet/object, corpus recall or lifecycle work, direct durableaoa-memolanding, or proof/scoring work
Inputs
- likely owner and stronger owner; task/closeout/landed-work context; inspectable session, source, PR, review, or receipt refs; local memo-port status; privacy, freshness, review posture, and confirmation that no concrete memo artifact already represents this writeback
Outputs
- one
memo_writeback_decision:write_candidate,prepare_export,no_writeback_needed,route_only_debt,needs_owner_review, orblockedorowner_handoff - when authorized, one guarded owner-local candidate or reviewed export packet; otherwise a no-write stop line or route-only debt with inspectable refs
Procedure
- Before reading this bundle, inspect only the request. If it already names or
supplies a concrete candidate, export, quarantine packet, memory object,
corpus identity, lifecycle target, or memory read-model target, do not load
this skill. Select
aoa-memodirectly. - After selection, the first tool turn must read only this bundle's
SKILL.mdfrom the exact absolute package path observed in the host catalog or returned by a verified owner resolver. Use that loaded package path as the source root for the references below. Catalog syntax such asfile:is only a locator presentation; a normalized absolute path is sufficient. Do not reconstruct the path from a presumed skill root,.system,$CODEX_HOME, the workspace, or the skill name. Do not combine the read withpwd,AGENTS, workspace inspection, or another command. An absent, malformed, non-absolute, or ambiguous catalog/resolver identity isblocked_package_path_not_observedbefore any other package or workspace action.
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.
- 1mo ago Changed · +9 lines efb1da9a1806
- 1mo ago First seen · 137 lines · 95 tokens per session scan A 5f53494e1e2b
aoa-memo-writeback is a skill published in the GitHub repository 8Dionysus/aoa-skills (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 95 tokens to every session and 1,672 once invoked, about $0.0004 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 skills, from other repositories
aoa-memo
AoA/Abyss durable memory and owner orientation: use when ongoing work may depend on reviewed prior decisions, provenance, lifecycle/currentness, or an existing memo artifact, even when none is named. Also use to recall, review, or evolve a candidate, export, quarantine packet, object, corpus identity, lifecycle…
git-ai-search
Search and restore AI conversation context from git history.
remember
Save the decisions, facts, dead ends and architecture this conversation established to Atlas's shared memory, so other agents and future sessions can build on them.
ctx
Use ctx as working memory for prior agent work. Before starting or continuing work in an unfamiliar area, resuming earlier work, or revisiting an investigation, search prior sessions to ground yourself in earlier context. Use ctx blame to trace a line, file, commit, or PR to the agent session that produced it. Use…
deja-search
Search deja before re-deriving past work: when the user refers to earlier sessions or decisions, before debugging an error, and before implementing something that may already exist. It searches this machine's own history across every AI coding tool used on it, going back further than deja itself was installed.
deja-history
Search the user's past AI coding sessions. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you…