LLM Mart Basic

Dispatched by the tribunal deep-audit lane's Phase 1, on a large/sprawling repo, to offload structural mapping out of the orchestrator's retained context. Read-only extractor, not a judge — reports facts, files no findings.

Dispatched when a database migration file is added or modified. Reviews migrations for safety, data-classification tagging, and immutability against .codearbiter/security-controls.md.

INTERNAL evidence-gatherer dispatched by the decision-variance and context-creation skills. Scans an assigned code scope and reports evidence of architectural decisions — file paths and line numbers only. Never dispatch directly.

Dispatch PROACTIVELY when a change touches authentication, authorization, cryptography, secrets, deployment manifests, network policies, or CI workflows. Reviews diffs against {{PROJECT_DIR}}/.codearbiter/security-controls.md. Read-only; produces findings.

Dispatched by the tribunal deep-audit lane, once per active lens, with a lens assignment. Generic read-only lens executor — reads the assigned lens mandate under skills/tribunal/references/lenses/ and writes one file per finding. Never dispatch directly.

Imported from arbiterforge/codearbiter/plugins/ca-pi/agents/INDEX.md.

Read-only checkpoint reviewer. Surfaces drift between the codebase and accepted ADRs in .codearbiter/decisions/. Informational — never blocks.

Reviews authentication, cryptography, key handling, and secrets against <project-root>/.codearbiter/security-controls.md. Hard blocks on banned primitives, exposed secrets, disabled TLS verification, and shell injection. Read-only checkpoint reviewer.

Use when writing or modifying backend/server-side code. Owns the TDD workflow, input validation, framework conventions, and ORM usage. MUST write failing tests before implementation code. Reads tech stack from <project-root>/.codearbiter/tech-stack.md.

Composes the finding-triage report and decision-challenger output into a dated checkpoint document under .codearbiter/checkpoints/YYYY-MM-DD.md. Aggregator, not a blocker.

Dispatched by the tdd skill (Phase 4) to audit test coverage against TDD obligations. Identifies untested source files, coverage below the maturity threshold, and logical test gaps.

Adversarial red-team reviewer of ADRs. Builds the strongest case against each decision, names load-bearing assumptions, assigns confidence 1–5, and surfaces evidence that would prove a decision wrong. Read-only. Dispatched optionally by decision-variance. Reads ADRs from .codearb

Dispatched when package.json, lock files, or container base images change. Verifies license, provenance, maintenance signal, and supply-chain posture against .codearbiter/security-controls.md and .codearbiter/tech-stack.md before merge.

Reviews generated, user-facing visual or formatted output (UI, reports, slides, charts, diagrams, CLI output) against the anti-slop-design reference. Read-only; surfaces design-slop findings. Dispatched by frontend-author on UI changes. Tier 2 document producers (/pr, release) ap

Post-processes all checkpoint reviewer reports — consolidates findings, classifies each by severity and whether it blocks the current change. Sequential. Produces a unified triage report for the checkpoint-aggregator. Reads project state from .codearbiter/.

Use when writing or modifying frontend/UI code. Owns the TDD workflow, component conventions, state management, and UI security. MUST write failing tests before implementation code. Reads tech stack from <project-root>/.codearbiter/tech-stack.md.

INTERNAL SMARTS analyst dispatched by the decision-variance skill. Produces a SMARTS analysis and recommendation for one (artifact-position, scaffold-evidence) pair. Never decides — the user decides. Never dispatch directly.

Use when writing or modifying IaC, containers, CI/CD manifests, or deployment configuration. Reads tech stack and security boundaries from <project-root>/.codearbiter/.

Dispatched by the tribunal deep-audit lane's Phase 1, on a large/sprawling repo, to offload dependency/integration-surface mapping out of the orchestrator's retained context. Read-only extractor, not a judge — reports facts, files no findings.

Dispatched by the tribunal deep-audit lane's Phase 1, on a large/sprawling repo, to offload structural mapping out of the orchestrator's retained context. Read-only extractor, not a judge — reports facts, files no findings.

Fourteen posts of being wrong in production, compressed to checkboxes

Healthy nodes, a quiet network, 300 restarts in three days, and a latency budget measured in milliseconds

Discovery worked. Ping worked. Every TCP connection timed out, and later the tunnel only worked when someone had a terminal open.

Every VM came back. The cluster did not. Declarative systems converge on config, and the datapath isn't config.

A surprising share of AI-in-the-terminal failures aren't the AI. They're zsh, and a version of bash from 2006.

A Claude Code plugin turns standalone project configuration into a namespaced, installable extension that teams and communities can update as one unit.

None of the safety came from the model. It came from six boring habits.

Skills package instructions and references. Subagents run work in a separate context and return results. They solve different problems and can be composed deliberately.

Six hours in, one step left, everything green, and the incident that didn't happen

CLAUDE.md carries persistent project context. Skills load reusable procedures when relevant. Separating stable facts from task-specific workflows keeps both easier to maintain.

Twenty minutes recovering secrets that never existed, and the one sentence from a human that ended it

An API request routing a model's tool call through an approval gate to a remote MCP server

31 config keys, two audits, and why the first one was wrong in both directions

The official MCP Registry stores standardized server metadata rather than package code. Publishers verify a namespace, describe installation or remote access, and submit immutable versions.

Everyone looks at the Dockerfile. The file that actually leaked the key was the project file.

Remote MCP authorization uses established OAuth standards, but secure integration still requires issuer validation, least-privilege scopes, protected token handling, and server-side enforcement.

"Copy it over and switch the reference" is two steps, and the outage lives in the one nobody checks

stdio fits local processes and prototypes. Streamable HTTP fits hosted services and shared integrations. The right choice follows where the capability runs and who must reach it.

The most important rule wasn't about what I could change. It was about what I was allowed to display.

Tools perform operations, resources expose readable context, and prompts provide reusable templates. Choosing the correct primitive makes an MCP server easier to understand and govern.

Consolidate MEMORY.md and Project Learnings: dedupe, resolve conflicts, prune

Explain Solana code with a diagram and a step-by-step walkthrough

Generate a typed client from an Anchor or Shank IDL (Codama or Anchor TS)

Migrate TypeScript from @solana/web3.js 1.x to @solana/kit

Plan a Solana feature before coding: accounts, PDAs, instructions, risks, tests

First-time-user product review: scorecard and fix roadmap; --harsh for a roast

Measure compute units per instruction and flag the expensive ones

Format, lint and commit with a conventional message on a kit-named branch

Resync external skill submodules to latest upstream versions

Scaffold a Solana project (Anchor, fullstack, frontend, Pinocchio) with the kit

Set up GitHub Actions CI for Solana programs: lint, build, test, audit

Configure MCP server API keys in .env and add the optional MCP servers

Run tests, auto-fix fmt and lint, and fix failures until green or stuck

Run C# tests: Unity Test Framework in batchmode, or dotnet test

Run Rust tests for programs (LiteSVM, Mollusk, Surfpool, Trident) and backends

Run TypeScript tests for programs (Anchor TS, Kit) and dApp frontends

Update solana-ai-kit to latest version from upstream

Write docs for a Solana program, SDK or component from its code and IDL

Seventy-two slash commands for Claude Code, grouped by what you are doing.

Find missing aliases

A systematic AI Agent development tutorial covering LLM agents, RAG, tool use, memory systems, multi-agent systems, LangChain, LangGraph, MCP, and agentic RL.｜从…

Convert Files / Folders / GitHub Repos Into AI / LLM-ready Files

Open-source, local-first conversational AI video editor with a professional multi-track timeline, Agent Skills, MCP integration, and Remotion rendering.

Maintainer-governed agent for evidence-backed open-source contribution proposals

A Claude Code skill by Hao (駱君昊) that learns your Facebook voice and auto-posts to FB / IG / Threads / X with a 14-day content calendar. Mega-viral validated: 8…

Local-first AI agent workspace for coding, writing, design, research, and automation — one runtime for desktop GUI and TUI.

Open-source AI Agent platform for teams. Your agents don't just chat — they read files, run code, call APIs, and deliver results.

Give your AI agent eyes for PDFs — structured text, tables, OCR, visual evidence, and page-level citations via MCP. Native Rust, local-first.

Real-world AI penetration testing engineer for authorized assessments — built-in cloud module covering AWS/Azure/GCP + Aliyun/Tencent/Huawei clouds. Built on Cl…

OpenGUI is an Android GUI agent framework for phone-use AI that can see, plan, and operate real mobile apps through the GUI.

Tinybot is a lightweight personal AI Agent that is constantly evolving

Goink 桌面 AI 小说创作助手，对话式写作 + 自动状态追踪 + 本地语义搜索。跨平台开箱即用。AI Agent Novel Generator.

Pluggable DeepSeek-colored TUI for DeepSeek Harness

Entity-level git merge driver. Resolves false conflicts git invents when independent agents edit the same file. ~95% reduction vs. line-based merge.

Percho: Minimalist desktop GUI for the Pi coding agent — the same engine as the Pi CLI, in a clean visual interface. Multi-session chat, visual tool approvals,…

Run Claude Code, Codex & Gemini in parallel on Windows & macOS — git worktree fan-out with atomic hunk adoption, approval gates, reboot-surviving sessions

A hierarchical memory framework for personalized presentation agents. Try it at memslides.com.

Real-time multimodal desktop agent evolving toward a persistent AI OS interface (0.1 α).

clawdcursor compiles whatever's on screen into one UI map — accessibility tree and OCR fused into stable, addressable elements, with a screenshot only when need…

Repeatable agentic engineering. The workflow layer that turns AI coding agents into a disciplined factory: durable specs, fresh-context workers, adversarial cro…