aristotle

aristotle is a skill for Claude Code, Codex from alexwwang/aristotle. It costs 209 tokens per session (1,433 once invoked), scanned A, original, MIT.

An error-reflection and learning workflow activated with /aristotle after someone reports a mistake or incorrect result.

In plain words
What is it for?
Use it to reflect on an agent's previous answer, review a numbered session, or start a learning workflow.
Why use it?
It provides a defined way to review what went wrong and learn from corrections.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/alexwwang/aristotle/skill
Any agent
npx skills add alexwwang/aristotle --skill skill
Clone the repo
git clone --depth 1 https://github.com/alexwwang/aristotle

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for aristotle

README.md
[![agentmods](https://agentmods.dev/badge/skills/alexwwang/aristotle/skill.svg)](https://agentmods.dev/skills/alexwwang/aristotle/skill)
Your own site
<a href="https://agentmods.dev/skills/alexwwang/aristotle/skill"><img src="https://agentmods.dev/badge/skills/alexwwang/aristotle/skill.svg" alt="Measured on agentmods" height="20"></a>
Per session 209 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,433 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00209 $0.01433
Opus 5 $0.00105 $0.00717
Sonnet 5 $0.00042 $0.00287
Haiku 4.5 $0.00021 $0.00143

Measured 5d ago against content hash 08d7579f9e51, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

aristotle 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 5d 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.

skill/SKILL.md · 98 lines

How it starts

The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Aristotle — Dispatcher

CRITICAL: DO NOT load REFLECT.md, REVIEW.md, LEARN.md, or CHECKER.md. All logic is handled by MCP orchestration tools. NEVER mention internal mechanism names (MCP tool names, action names, workflow_id, prompt fields) to the user — describe outcomes in plain language only.

ROUTE

cmd = first argument or ""
MATCH cmd:
  "learn"    → CALL orchestrate_start("learn", args_json) → execute ACTION
  "sessions" → CALL orchestrate_start("sessions", "{}") → execute ACTION
  "review"   → CALL orchestrate_start("review", {sequence: N}) → execute ACTION → REVIEW FEEDBACK
  *          → GOTO PRE-RESOLVE

PRE-RESOLVE (reflect only)

result = CALL orchestrate_start("reflect", {target_session_id: "", session_file: "",
  focus: "last", user_language: <detect>, project_directory: <cwd>})

MATCH result.action:
  "fire_sub"  → Bridge handles snapshot. execute ACTION. STOP.
  "pre_resolve_needed" → GOTO SNAPSHOT-EXTRACT
  "notify"    → Display result.message. STOP.
  other       → execute ACTION. STOP.

## SNAPSHOT-EXTRACT (non-Bridge / Claude Code only)
IF session_list is available:
  target_session_id = session_list()[0].id
  content = session_read(target_session_id)
  Bash("mkdir -p ~/.config/opencode/aristotle-sessions")
  Write snapshot JSON (schema v1, source: "llm-session-read") to
    ~/.config/opencode/aristotle-sessions/{target_session_id}_snapshot.json
  session_file = that path
ELSE:
  session_file = ""
IF any step fails: session_file = ""

result = CALL orchestrate_start("reflect", {target_session_id, session_file,
  focus: "last", user_language: <detect>, project_directory: <cwd>})
→ execute ACTION. STOP.

ACTION EXECUTION

If action is pre_resolve_needed:

GOTO SNAPSHOT-EXTRACT (in PRE-RESOLVE section above).

If action is fire_o:

  1. Call task(category="unspecified-low", run_in_background=true, prompt=o_prompt)
  2. When notification arrives, call MCP orchestrate_on_event("o_done", {workflow_id, result})
  3. Execute returned action per this section

Read the full file on GitHub · 98 lines

Files

What ships with it

5 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.

Changes

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.

  1. 5d ago First seen · 98 lines · 209 tokens per session scan A 08d7579f9e51

Subscribe to this mod's changes

aristotle is a skill published in the GitHub repository alexwwang/aristotle (17 stars, last pushed 4d ago), licensed MIT. It adds 209 tokens to every session and 1,433 once invoked, about $0.0010 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens