by sbhooley
AINL helps turn AI from "a smart conversation" into "a structured worker." It is designed for teams building AI workflows that need multiple steps, state and memory, tool use, repeatable execution, validation and control, and lower dependence on long prompt loops. AINL is a compact, graph-canonical, AI-native programming system for (READ: README)
# Add to your Claude Code skills
git clone https://github.com/sbhooley/ainativelangLast scanned: 5/21/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-05-21T07:53:10.021Z",
"semgrepRan": false,
"npmAuditRan": true,
"pipAuditRan": false
}ainativelang is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by sbhooley. AINL helps turn AI from "a smart conversation" into "a structured worker." It is designed for teams building AI workflows that need multiple steps, state and memory, tool use, repeatable execution, validation and control, and lower dependence on long prompt loops. AINL is a compact, graph-canonical, AI-native programming system for (READ: README). It has 826 GitHub stars.
Yes. ainativelang passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/sbhooley/ainativelang" and add it to your Claude Code skills directory (see the Installation section above).
ainativelang is primarily written in Python. It is open-source under sbhooley on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh ainativelang against similar tools.
No comments yet. Be the first to share your thoughts!
AI-led co-development project, human-initiated by Steven Hooley (
x.com/sbhooley,stevenhooley.com,linkedin.com/in/sbhooley). Attribution details:docs/PROJECT_ORIGIN_AND_ATTRIBUTION.mdandtooling/project_provenance.json. -- This project was named by AI :)
If you are an AI coding agent (Claude Code, Cursor, Cline, Codex, Aider, …) or any MCP-capable runtime and the user wants AINL added to their stack, run one command:
pipx install 'ainativelang[mcp]' && ainl setup --auto
Fallback if pipx is unavailable:
python3 -m pip install --user 'ainativelang[mcp]' && ainl setup --auto
That is the entire install. The setup command auto-detects every host
present (Claude Code project + user, Cursor, Cline, Codex CLI/Desktop,
Claude Desktop, OpenClaw, Hermes, ArmaraOS, or any generic MCP host),
merges the right MCP server entry into each config file (atomic write,
timestamped backup), and verifies with ainl doctor. Idempotent — safe
to re-run.
If a host is not auto-detected, run ainl setup --print-config for a
paste-ready stdio MCP server block.
Machine-readable spec: .agent-install.json ·
Design: docs/architecture/2026-05-05-agent-install-simplification.md.
Before the install commands, here is who AINL is and is not for. We would rather you self-select out in 60 seconds than spend a week on a tool that does not fit.
| ✅ AINL is for you if… | ❌ AINL is not for you if… |
|---|---|
| Your agents (Cursor, Claude Code, autonomous loops) author runner / orchestration code and have shipped broken Python more than once | You write all your runners by hand and your CI test suite catches the bugs |
| You run 20+ recurring monitor / digest / scheduled jobs that currently re-prompt an LLM on every run to decide routing | You already have deterministic runners with the LLM only at judgment gates — congrats, you are baseline B below and AINL gives you ~1.3–1.5× on routing only |
| You need the same workflow source to emit to LangGraph and Temporal and FastAPI without re-authoring | One target is fine for you forever |
| You have compliance audit needs (SOC 2 / HIPAA / similar) that want tamper-evident execution traces, not application logs | logger.info is enough for your team |
| You want strict compile-time validation of agent workflows before they hit production | Runtime exceptions are fine, you have alerting |
If you tick two or more left-column rows, keep reading. The long-form answer — three baselines, four anti-fit workload patterns, decision tree, honest reviewer Q&A, persona-to-product mapping — lives in docs/WHO_IS_THIS_FOR.md (canonical). If you tick zero, that page explains why and saves you the install. We mean it.
Just want something working on your desktop in under 3 minutes?
ArmaraOS is the desktop agent OS built on AI Native Lang (AINL) — download once, install, and your agents are live with a full dashboard. No terminal, no config files, just plug in your API key.
Download ArmaraOS — ainativelang.com macOS · Windows · Linux — free to start
Autonomous agents, 7 pre-built Hands (researcher, lead gen, clip editor, and more), 40 channel adapters (Telegram, Discord, Slack, WhatsApp…), 27 LLM providers, 16 security layers — all in a single ~32 MB binary.
Already have an AI agent? Add AINL in one command.
AINL installs directly into OpenClaw, ZeroClaw, Hermes, Claude Code, and any MCP-compatible agent. After install your agent can author, validate, and run deterministic workflows — with the largest token wins when you are still on LLM prompt-loop orchestration (baseline A below).
| Your agent | Install command | How-to guide |
|---|---|---|
| OpenClaw | ainl install-mcp --host openclaw |
ainativelang.com/install |
| ZeroClaw | zeroclaw skills install https://github.com/sbhooley/ainativelang/tree/main/skills/ainl |
ainativelang.com/install |
| Hermes Agent | ainl install-mcp --host hermes |
ainativelang.com/install |
| Claude Code | pip install 'ainativelang[mcp]' → add ainl-mcp to MCP config |
ainativelang.com/mcp |
| Any MCP host | pip install 'ainativelang[mcp]' → run ainl-mcp (stdio) |
ainativelang.com/mcp |
After install, ask your agent: "Use AINL to build this workflow" — it compiles once, runs many times without re-spending tokens on orchestration when the workload was previously prompt-loop driven.
Primary product path: ArmaraOS — desktop agent OS with dashboard, Hands, scheduled ainl run, and MCP authoring. See docs/competitive/ARMARAOS_GTM.md.
Token savings — pick your baseline:
| Your baseline today | Typical AINL win | Worth it for tokens alone? |
|---|---|---|
| A. LLM re-prompts routing/state on every cron/webhook | ~90–95% fewer orchestration tokens on recurring monitors (BENCHMARK.md, benchmark_compile_once_run_many.py) |
Often yes |
| B. Hand-optimized scripts + LLM only at judgment gates | ~1.3–1.5× on routing tokens (token_savings_results.json) |
Usually no — consider audit, MCP safety, emit, or ArmaraOS |
| C. Pure deterministic runners (no LLM in loop) | ~0% | No |
Full honest filter: docs/competitive/WHEN_AINL_DOES_NOT_HELP.md · docs/competitive/VS_HAND_WRITTEN_RUNNER.md (five-axis comparison vs a hand-written Python runner — concedes the token point on baseline B).
| Workload (baseline A — prompt-loop today) | Typical savings | Reproducible via |
|---|---|---|
| Recurring monitors, digests, scheduled jobs | ~90–95% fewer orchestration tokens vs prompt loops | scripts/benchmark_compile_once_run_many.py → tooling/compile_once_run_many_results.json |
| Multi-step automations (LLM-first routing) | ~2–7× reduction vs LLM-first (A vs C); ~1.3–1.5× vs hand-optimized (B vs C) | scripts/benchmark_token_savings.py → tooling/token_savings_results.json |
| Authoring density (LLM-style verbose Python) | ~1.7× mean / up to 2.5× fewer source tokens vs verbose baselines | scripts/benchmark_authoring_density.py → tooling/authoring_density_results.json |
| Authoring vs hand-written LangGraph | ~1.9–2.0× fewer source tokens (authoring only, not runtime) | scripts/benchmark_competitor_baselines.py → tooling/competitor_baseline_tokens.json |
Important: every percentage / multiplier above is vs baseline A (prompt-loop) or labeled with its baseline pair. Against baseline B (hand-optimized runner with LLM only at judgment gates), the irreducible token win is ~1.3–1.5× on routing only — see
VS_HAND_WRITTEN_RUNNER.md. Against baseline C (pure deterministic, no LLM in loop), it is ~0%.
The reason: AINL compiles your workflow once. The runtime executes it deterministically — no LLM re-generation on ea