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-agents --skill aoa-session-progression-liftgit clone --depth 1 https://github.com/8Dionysus/aoa-agentsWrote 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-agents/aoa-session-progression-lift)<a href="https://agentmods.dev/skills/8dionysus/aoa-agents/aoa-session-progression-lift"><img src="https://agentmods.dev/badge/skills/8dionysus/aoa-agents/aoa-session-progression-lift/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-agents/aoa-session-progression-lift"><img src="https://agentmods.dev/badge/skills/8dionysus/aoa-agents/aoa-session-progression-lift.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.00062 | $0.01314 |
| Opus 5 | $0.00031 | $0.00657 |
| Sonnet 5 | $0.00012 | $0.00263 |
| Haiku 4.5 | $0.00006 | $0.00131 |
Grade A, and why
aoa-session-progression-lift 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 11d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aoa-session-progression-lift
Intent
Make observed agent growth legible without turning one success, a mood, or a
generated summary into progression truth. The result is an owner-review
candidate; aoa-agents keeps progression authority and aoa-evals keeps proof.
Owner-source return
Resolve the canonical aoa-agents root before any owner-relative read:
- Record
<bundle_dir>as the absolute directory containing theSKILL.mdactually loaded; never resolve from the task working directory. Initialize one unresolved<source_route>and<owner_root>. - In one tool turn containing no other read or command, inspect exactly one
same-bundle handle:
<bundle_dir>/.aoa-skill-source.json. Await its result. If it is a regular file, set<source_route>tosource-handleand require schemaaoa_skill_source_receipt_v1oraoa_skill_source_receipt_v2, this bundle name, owneraoa-agents, version0.2.5, an existing absoluteowner_root, a safe relativesource_path, and<owner_root>/<source_path>/SKILL.md. For v2 also require non-emptydigest,source_fingerprint,source_fingerprint_scope, andprompt_description_sha256. Whencapability_graph_hashis present, require it to be a non-empty string and preserve it. If the path exists but is invalid, mismatched, or not a regular file, returnblocked_missing_owner_source; do not try another location. - Only when that exact same-bundle handle path does not exist, set
<source_route>togitand rungit -C <bundle_dir> rev-parse --show-toplevelexactly once. Require the returned root'sskills/port.manifest.jsonto declare the expected owner, bundle, and path. - In the next tool turn, read only
<owner_root>/skills/port.manifest.json; do not include an owner document, bundle reference, evidence read, or unrelated command in that tool turn. Await the manifest result. In the source-handle branch, require the sameowner_repo, bundle name, and bundlepathas the handle. In the git branch, requireaoa-agents, this bundle name, and its actual bundle path. If the manifest read shared a tool batch with an owner document, the serial gate was not observed: returnblocked_owner_source_gate_not_observedand do not use either result. - Only after the successful manifest result, use a later tool turn to read
exactly the two named owner-model documents below. Then owner-source
resolution is complete. Do not run or retry the other source branch,
including after a later owner-document read fails. Any handle, git,
manifest, path, or owner mismatch returns
blocked_missing_owner_sourceand ends this invocation. - Never use
find,rg --files, parent traversal, sibling scans, workspace conventions, temporary fixtures,.system, or another skill directory to discover a substitute owner root.
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.
- 11d ago First seen · 110 lines · 62 tokens per session scan A eff4cf40d70d
aoa-session-progression-lift is a skill published in the GitHub repository 8Dionysus/aoa-agents (3 stars, last pushed 3d ago), licensed Apache-2.0. It adds 62 tokens to every session and 1,314 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-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…
aoa-memo-writeback
Use only before any memo artifact exists to decide whether live-session, closeout, landed-work, PR, diff, or review evidence yields one guarded memo candidate, export, or no-write result. If a concrete memo candidate, export, object, corpus, lifecycle, or read-model target already exists, use aoa-memo. Do not use for…
aoa-eval
Select or apply an owner-local or cross-repository eval, route a confirmed no-fit to intake/design, or classify supplied session hits as eval candidates. Do not use for central proof bundles, named results or verdicts, source-linked reports, proof lifecycle, ordinary tests, undefined invariants, or generic session…
aoa-checkpoint-closeout-bridge
Carry provisional checkpoint hints into a reviewed session closeout: harvest, progression, quest-promotion, and branch handoff. Use to collect bounded hints or execute after the current session artifact is closed and reviewed. Do not use mid-session for final judgment, without reviewed evidence, as a hidden playbook…
aoa-knowledge-stewardship
Sanitize private technical material into a public-safe owner-bounded derivative, or resolve authority among authored, generated, runtime, and installed sources. Use for governed incidents, logs, configs, diagnostics, or conflicting source roles. Do not use for ordinary editing, memo/session work, direct publication…
aoa-decision
Find, record, correct, or supersede a durable repository decision and its derived indexes. Use for prior rationale, a meaningful accepted choice, or decision-source/index drift. Do not use for ordinary documentation, an open choice, current source-authority conflicts, or runtime/generated authority mapping.