Skip to content
Agentmart
Submit a tool

aizen-core

Shared core of the Aizen suite (v26) — authority levels A0–A4, evidence labels, decisions and options, git and local-only hand-off, code quality (least code…

Skill by tankhangkm12

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/tankhangkm12-aizen-core

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Shared core of the Aizen suite (v26) — authority levels A0–A4, evidence labels, decisions and options, git and local-only hand-off, code quality (least code, the reuse ladder), numbers and projections, workspace layout, the quality gate (check.py), the code map (graph.py) and capacity projections. Loaded by every Aizen skill through its brief or its "Read first" line; not a standalone skill, do not trigger it directly.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found
Runs as
Python package

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/aizen-core

What's inside

Skill name
aizen-core
Description
Shared core of the Aizen suite (v26) — authority levels A0–A4, evidence labels, decisions and options, git and local-only hand-off, code quality (least code, the reuse ladder), numbers and projections, workspace layout, the quality gate (check.py), the code map (graph.py) and capacity projections. Loaded by every Aizen skill through its brief or its "Read first" line; not a standalone skill, do not trigger it directly.
License
MIT
Instructions
53 lines in SKILL.md · view on GitHub

Before installing

  • Ships executable scripts

Agent Skills spec issues

  • files: referenced but missing: references/review/code.md, references/dev/out-of-scope.md

Files (38)

  • SKILL.md
  • contract.default.json · assets/core/
  • evidence-record.json · assets/core/
  • pr-draft-template.md · assets/core/
  • manifest.json
  • challenge.md · references/core/
  • code-map.md · references/core/
  • code-quality.md · references/core/
  • code-style.md · references/core/
  • decisions.md · references/core/
  • docs.md · references/core/
  • evidence.md · references/core/
  • git-handoff.md · references/core/
  • git.md · references/core/
  • mcp.md · references/core/
  • numbers.md · references/core/
  • reasoning.md · references/core/
  • rules.md · references/core/
  • LICENSE · references/core/vendor/karpathy-guidelines/
  • UPSTREAM.md · references/core/vendor/karpathy-guidelines/
  • examples.md · references/core/vendor/karpathy-guidelines/
  • guide.md · references/core/vendor/karpathy-guidelines/
  • verifier.md · references/core/
  • workspace.md · references/core/
  • continuous-improvement.md · rules/
  • evolution.md · rules/
  • isolation.md · rules/
  • reasoning.md · rules/
  • search-strategy.md · rules/
  • working-principles.md · rules/
  • capacity.py · scripts/core/
  • check.py · scripts/core/
  • docs.py · scripts/core/
  • graph.py · scripts/core/
  • guard.py · scripts/core/
  • guard_selfcheck.py · scripts/core/
  • journal.py · scripts/core/
  • project.py · scripts/core/

SKILL.md (first lines)

# Aizen core — the rules every Aizen skill shares (v26)

One copy of the rules that used to be repeated in every skill. Entry skills (`aizen-build`, `aizen-init`, …)
and knowledge packs point here instead of restating them.

**Read first:** `references/core/rules.md` — authority, questions, lanes, code, git, evidence, output.

## What lives here

| Need | Read / run |
|---|---|
| who may do what (A0–A4), when to ask, `BLOCKED` / `HANDOFF` | `references/core/rules.md` |
| how to reason before acting: frame, facts, options, failure, smallest step; playbooks for bugs, design, unknown tools, performance, data/money/concurrency, being stuck | `references/core/reasoning.md` (short form: `rules/reasoning.md`, a session rule) |
| options, recommendations, research before proposing | `references/core/decisions.md` |
| least code, the reuse ladder, size signals, `ponytail:` debt markers | `references/core/code-quality.md` |
| comments, functions, naming — language-independent style | `references/core/code-style.md` |
| evidence labels, report shape, numbers with sources | `references/core/evidence.md`, `references/core/numbers.md` |
| challenging an upstream artifact | `references/core/challenge.md` |
| branches, backups, rollback; local-only hand-off and PR text | `references/core/git.md`, `references/core/git-handoff.md` |
| where files live (`.aizen/`), source priority, vendored knowledge | `references/core/workspace.md` |
| MCP tools (context7, sequentialthinking) | `references/core/mcp.md` |
| code map: who calls what, blast radius | `references/core/code-map.md` → `scripts/core/graph.py` |
| quality gate: lint, types, build, tests, secrets, deps → evidence JSON | `scripts/core/check.py` |
| run contract: sheet, rules, verifier, hooks, backlog — the gate that decides done | `scripts/core/guard.py` · `references/core/verifier.md` · `assets/core/contract.default.json` |
| team docs in `docs/` (one layout, readable on GitHub), where each design doc lives, index, check, migrate | `references/core/docs.md` · `scripts/core/docs.py` |
| the project map `.aizen/PROJECT.md` (one file, table of contents) | `scripts/core/project.py` · `references/core/workspace.md` |
| the run's journal in plain words, the owner's hand-off file `.aizen/out/latest.md` | `scripts/core/journal.py` · `references/core/rules.md` → Journal, Output |
| capacity, growth, contention projections | `scripts/core/capacity.py` |
| templates | `assets/core/pr-draft-template.md`, `assets/core/evidence-record.json` |

## Working principles — Karpathy's four, and where Aizen enforces each

The behavioural guidelines from [andrej-karpathy-skills](https://github.com/multica-ai/andrej-karpathy-skills)
(MIT, vendored with worked examples in `references/core/vendor/karpathy-guidelines/`). Aizen states each one in its
own rules so it is checked, not just recommended:

| Principle | In Aizen | Checked by |
|---|---|---|
| **Think before coding** — state assumptions, show interpretations, push back with a simpler option, stop when unclear | plan time only: every question in the plan with options and a default (`references/core/rules.md` Questions, `references/core/decisions.md`); the plan's "Simpler option" line; facts are measured, labelled `[verified]/[inferred]/[unverified]` | the owner confirms part by part; `state.py approve` refuses unconfirmed modules |
| **Simplicity first** — minimum code, nothing speculative, no single-use abstractions, no handling of impossible cases | `references/core/code-quality.md` §1: reuse ladder, items 5–5b, the "senior engineer / 200 → 50" question | reviewer simplicity check (`references/review/code.md` axis 7) |
| **Surgical changes** — touch only what you must, match the style, clean up only your own orphans, mention other dead code | `references/core/code-quality.md` §1 items 1, 3 and "every changed line traces to the request"; `references/dev/out-of-scope.md` | reviewer: lines tracing to no id, churn, deleted or "improved" pre-existing code |
| **Goal-driven execution** — turn the task into checks, test first, `step → verify` | each plan module carries its Tests and Done; `dev` makes them runnable before coding (aizen-build, dev role, step 3); `check.py` evidence | tester and reviewer judge against the plan at a pinned SHA |

Trade-off, as upstream says: the rigor is for non-trivial work. A typo fix or an obvious one-liner still gets a
smallest diff and a check, not a ceremony — size changes the plan, not the principles.

## Paths

Every Aizen path `references/<topic>/…`, `assets/<topic>/…` or `scripts/<topic>/…` belongs to the skill whose
`manifest.json` lists `<topic>` under `topics`. This pack owns `core`. Run scripts by absolute path:
`uv run "<CORE_DIR>/scripts/core/check.py" …` (`<CORE_DIR>` = this skill's folder; a brief prints it).

From tankhangkm12/Aizen-Skills, MIT.

More from tankhangkm12/Aizen-Skills

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Oct 8, 2026 (21 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from tankhangkm12

Cite this page

aizen-core skill. Agent Mart. https://agentmart.dev/skills/tankhangkm12-aizen-core (last updated 2026-10-24)