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 Ryan529616/aoi-orgware --skill claudegit clone --depth 1 https://github.com/Ryan529616/aoi-orgwareWrote 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/ryan529616/aoi-orgware/claude)<a href="https://agentmods.dev/skills/ryan529616/aoi-orgware/claude"><img src="https://agentmods.dev/badge/skills/ryan529616/aoi-orgware/claude.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.00081 | $0.01790 |
| Opus 5 | $0.00041 | $0.00895 |
| Sonnet 5 | $0.00016 | $0.00358 |
| Haiku 4.5 | $0.00008 | $0.00179 |
Grade A, and why
aoi 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 7d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operating under AOI
This project is governed by AOI (Agent Organization Infrastructure). AOI is a cooperative, fail-open procedural guardrail — not a sandbox. It keeps parallel agent work from overwriting ownership, losing decisions, or being closed without evidence. Work with it: the fastest path is to follow the loop below, not to route around the hooks.
The hooks will tell you the current state. Read what they say each turn.
First: bind this session to a task
On session start the hook prints one of:
-
"AOI is active … No unambiguous task mapping exists for this session." — the repo is governed but this chat is not yet bound to a task. Before any material edit, either resume an existing task or create one, then bind:
aoi status # see existing tasks aoi resume --task <task-id> # if continuing one # …or create a new one (see the loop below), then: aoi bind-session --task <task-id> --session-id <this-session-id> -
"This session is bound to task …" — run
aoi resume --task <id>and reconstruct from the task checkpoint and current files, not from memory.
Read-only answers (explaining code, summarizing) do not require a task. Only bind before material mutation or an external action.
The governed task loop
# 1. Create a task and make its plan explicit.
aoi init-task --task-id <id> --title "<title>" --objective "<why>" \
--owner root --completion-boundary "<what 'done' concretely means>"
$EDITOR .aoi/tasks/<id>/plan.md
aoi approve-plan --task <id> --note "Scope and verification are explicit"
# 2. Claim the EXACT write scope before you mutate anything.
aoi claim --task <id> --token <id>-claim --owner root --kind implementation \
--lock repo:file:path/to/file --intent "<what/why>" \
--validation "<how it will be checked>" --expires-at <tz-aware-timestamp>
# 3. Do the work, then record real evidence (see "Evidence" below).
# 4. Account for delivery, release the claim, checkpoint, and close.
aoi set-delivery --task <id> --mode local-only --detail "<where the change lives>"
aoi release-claim --token <id>-claim --status done --reason "<done>"
aoi checkpoint --task <id> --next-action "Close the task"
aoi close-task --task <id> --summary "<result>"
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.
- 7d ago First seen · 156 lines · 81 tokens per session scan A 578af1255b15
aoi is a skill published in the GitHub repository Ryan529616/aoi-orgware (2 stars, last pushed 14d ago), licensed MIT. It adds 81 tokens to every session and 1,790 once invoked, about $0.0004 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
takt
A workflow engine that runs a task through a sequence of steps defined in a YAML file, using separate coding agents for the work.
takt
A workflow engine for coordinating multiple coding agents. It reads a YAML workflow, a text configuration format, and moves agents through its defined steps and rules.
company-product-context
Compiles comprehensive company product context from PDF documents, web research, and industry knowledge.
codebase-context-extractor
This skill provides a comprehensive context extraction system for large codebases. It intelligently analyzes code structure, dependencies, and relationships to extract relevant context for understanding, debugging, or modifying code.
skill-creator
Generates Anthropic Skills with complete workflow including GitHub PR creation and local download verification.
Research Synthesis Workflow
A step-by-step guide to synthesizing research from multiple sources into a coherent summary.