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-summongit 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-summon)<a href="https://agentmods.dev/skills/8dionysus/aoa-agents/aoa-summon"><img src="https://agentmods.dev/badge/skills/8dionysus/aoa-agents/aoa-summon/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-summon"><img src="https://agentmods.dev/badge/skills/8dionysus/aoa-agents/aoa-summon.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.00063 | $0.01256 |
| Opus 5 | $0.00032 | $0.00628 |
| Sonnet 5 | $0.00013 | $0.00251 |
| Haiku 4.5 | $0.00006 | $0.00126 |
Grade A, and why
aoa-summon 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 3d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aoa-summon
Execute an already settled actor route. This leaf does not form an obligation, choose a role or model, select unresolved transport, or widen the caller's authority. A plan is not a launch; execution needs an inspected host binding, a real runtime handle, output validation, and responsibility closeout. This is not the front door for generic delegation or native Codex helpers.
Owner source
Resolve from the absolute directory containing the loaded SKILL.md, not
from the task working directory:
- Inspect that bundle's
.aoa-skill-source.json. An existing handle must be a regular non-symlink file with schemaaoa_skill_source_receipt_v1oraoa_skill_source_receipt_v2, nameaoa-summon, owneraoa-agents, a non-empty version, an existing absoluteowner_root, and safe relativesource_pathcontainingSKILL.md. V2 also requires non-emptydigest,source_fingerprint,source_fingerprint_scope, andprompt_description_sha256; preserve a non-emptycapability_graph_hashwhen present. - Only if the handle is absent, use
git -C <bundle_dir> rev-parse --show-toplevelto locate the source root. - Read
<owner_root>/skills/port.manifest.json. Its owner, bundle name, path, and declared version must match the handle, or the source bundle'sreferences/contract.yamlwhen using Git. An invalid handle or mismatched manifest returnsblocked_missing_owner_source; do not search for a substitute checkout.
These are data dependencies, not separate-tool-turn requirements: dependent reads may share one call when each result is checked before using it. Record the resolved owner and source identity. Install digests and commit refs are provenance, not proof of current parity or execution.
For summon-boundary meaning, read the resolved owner's
mechanics/titan/parts/summon-boundary/README.md and its
docs/summon-boundary.md and docs/summon-protocol-v2.md.
Schema and compiler mechanics remain in this bundle.
Request and mode
What ships with it
17 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.
- agents/openai.yaml 365 B
- references/actor-responsibility-execution-receipt.schema.json 16 KB
- references/actor-route-preparation-result-v1.schema.json 1.0 KB
- references/actor-route-preparation-v1.schema.json 7.4 KB
- references/contract.yaml 14 KB
- references/lane-and-return.md 21 KB
- references/summon-request-v3.schema.json 10 KB
- references/summon-request-v4.schema.json 19 KB
- references/summon-result-v3.schema.json 25 KB
- references/summon-result-v4.schema.json 39 KB
- scripts/build_summon_v4_schemas.py 10 KB runs code
- scripts/compile_actor_responsibility_receipt.py 44 KB runs code
- scripts/compile_external_execution_request.py 41 KB runs code
- scripts/compile_external_execution_result.py 98 KB runs code
- scripts/prepare_external_actor.py 53 KB runs code
- scripts/publish_actor_responsibility_receipts.py 15 KB runs code
- scripts/validate_summon_request.py 11 KB runs code
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.
- 3d ago Changed · -11 lines 003d31b9c277
- 4d ago Changed · -295 lines · -118 tokens per session b74f762e6179
- 8d ago First seen · 415 lines · 181 tokens per session scan A 987a64b86ce4
aoa-summon is a skill published in the GitHub repository 8Dionysus/aoa-agents (3 stars, last pushed 3d ago), licensed Apache-2.0. It adds 63 tokens to every session and 1,256 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-04.
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.