Do we think this was a mistake? ----

node_modules/@anthropic-ai/claude-agent-sdk/cli.js.

  It's the bundled, minified CLI binary for Claude Code itself (the tool you're talking to right now).

  Key details:
  - Version: 2.1.71, built on 2026-03-06
  - ~13,800 lines of heavily minified/bundled JavaScript
  - Shebang: #!/usr/bin/env node — it's meant to be run as a CLI executable
  - Copyright: Anthropic PBC, with a cheeky note: "Want to see the unminified source? We're hiring!"
  - What it contains: The entire Claude Code CLI application bundled into a single file, including:
    - Onboarding/setup screens
    - Policy/managed settings loading
    - Debugging/inspector detection
    - UI rendering (using Ink/React for terminal UI)
    - Prefetching logic
    - Error handling and exit codes
    - The main entry point (main function) that starts the interactive Claude Code session

  Essentially, when you run claude in your terminal, this is the file that executes. The @anthropic-ai/claude-agent-sdk package ships it so you can
  programmatically invoke Claude Code's capabilities — the SDK wraps this CLI as its underlying engine.

  1. i6z function — This is the in-process agent runner, which logs "Starting agent loop for ${agentId}". It sets up agent identity (agentId,
  parentSessionId, agentName, teamName, color, planMode) and runs the loop.
  2. l6z function — A poll loop for in-process teammate agents. It continuously checks for:
    - Pending user messages
    - Mailbox messages from other agents
    - Shutdown requests
    - New tasks from the task list
  3. Main loop model orchestration — There's extensive logic around mainLoopModel that handles:
    - Model selection based on permission mode (plan mode uses Opus, etc.)
    - System prompt assembly (tools, MCP instructions, skills, memory, changed files)
    - Token usage tracking and budget management
    - Compaction (context window management when conversations get long)
  4. Multi-agent coordination — The loop supports a team-based agent architecture with messaging between agents (agentName, teamName, teamLead, mailboxes,
  shutdown requests).

  So yes — the full agentic loop (prompt → LLM call → tool execution → repeat) is bundled in this file, just heavily minified. It's the same loop powering
  this conversation right now.

  Three identity variants:

  - F78 — CLI mode: "You are Claude Code, Anthropic's official CLI for Claude."
  - EtA — SDK mode: "You are Claude Code, Anthropic's official CLI for Claude, running within the Claude Agent SDK."
  - LtA — Agent mode: "You are a Claude agent, built on Anthropic's Claude Agent SDK."

  Full system prompt sections (line ~6213-6217):

  The ULz function assembles the complete system prompt, including all the sections you'd recognize:

  - "# Doing tasks" — instructions about software engineering, not proposing changes to unread code, avoiding over-engineering, OWASP security, etc.
  - Over-engineering rules — "Don't add features beyond what was asked", "Don't add error handling for scenarios that can't happen", "Don't create helpers
  for one-time operations"
  - Help/feedback info — links to GitHub issues
  - Tool usage instructions — Read vs cat, Edit vs sed, etc.

  Output style variants (line ~6517):

  Built-in output styles like Explanatory and Learning with their own prompt overlays.

  Also present:

  - The classifier/safety prompt (~line 2844) for security-relevant harm prevention
  - Subagent instructions like "You ARE the fork. Do NOT spawn sub-agents"
  - Git commit/PR workflow prompts
  - Memory system instructions

Comments URL: https://news.ycombinator.com/item?id=47285571

Points: 1

# Comments: 1

I distilled multiple software books into these flows and skills. With more books to come.

Here is an example https://github.com/ryanthedev/code-foundations

I imagine some more like. https://github.com/ryanthedev/code-foundations

Based of an actual software book.

https://github.com/ryanthedev/code-foundations

I’m currently working on a checklist and profile based code review system.

Comments URL: https://news.ycombinator.com/item?id=46575830

Points: 1

# Comments: 1

It's really going to be interesting to see how this tech evolves.

Now that you mention it, i can see a future where claude may offer a "skills" feature and codex offers a "talent" feature. where they are essentially the same things, but specific to that vendor.

reminds me how each cloud has the same offerings but different products.

At some point I plan to do some ralph wiggum loop stuff maybe to hash out the best way for triggers to work.

It's more than a single prompt, but less than an entire agent. I find skills to be the tools you use on the fly. Like how I might have a wrench,screw-driver, hammer in my tool box.

tools vs skills is all about context efficiency from what I see. and yes, this isn't novel of claude. but they are the first to offer this abstraction.

That's what I have been doing as I'm building these skills out. There is a really fun testing/tdd loop that runs these skills through multiple prompts with baselines and tests it all out.

Comments URL: https://news.ycombinator.com/item?id=46531794

Points: 92

# Comments: 33