LLM Mart Basic
@llm-mart · Joined Jun 2026
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-root>/.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/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 ${CLAUDE_PROJECT_DIR}/.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 ${CLAUDE_PROJECT_DIR}/.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 ${CLAUDE_PROJECT_DIR}/.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 ${CLAUDE_PROJECT_DIR}/.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.
Dispatched when a database migration file is added or modified. Reviews migrations for safety, data-classification tagging, and immutability against .codearbiter/security-controls.md.
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.
/doc-api
Doc api
Generate API documentation from code
/docs
Docs
Update or generate YAML documentation for SQL models with proper descriptions and tests
/e2e-setup
E2e setup
Configure end-to-end testing suite
/estimate-assistant
Estimate assistant
Generate accurate project time estimates
/explain-code
Explain code
Analyze and explain code functionality
/explain-issue-fix
Explain issue fix
Explain how tasks in an issue were implemented with detailed breakdown
/find
Find
Search and locate tasks across all orchestrations using various criteria.
/five
Five
Apply the Five Whys root cause analysis technique to systematically investigate issues
/fix-github-issue
Fix github issue
Analyze and fix a GitHub issue with comprehensive testing and verification
/fix-issue
Fix issue
Fix a specific issue or problem with the given identifier or description
/fix-pr
Fix pr
Fetch unresolved comments for current branch's PR and fix them
/future-scenario-generator
Future scenario generator
Generate and analyze future scenarios with plausibility scoring, trend integration, and uncertainty quantification.
/generate-api-documentation
Generate api documentation
Auto-generate API reference documentation
/generate-linear-worklog
Generate linear worklog
You are tasked with generating a technical work log comment for a Linear issue based on recent git commits.
/generate-test-cases
Generate test cases
Generate comprehensive test cases automatically
/generate-tests
Generate tests
Generate comprehensive test suite for $ARGUMENTS following project testing conventions and best practices.
/git-status
Git status
Show detailed git repository status
/hotfix-deploy
Hotfix deploy
Deploy critical hotfixes quickly
/husky
Husky
Verify repository is in working state by running CI checks and fixing issues
/implement-caching-strategy
Implement caching strategy
Design and implement caching solutions
Open-source, self-hosted AI media server. One server replaces your entire media stack, with a web app, native iPhone app, and an AI agent that gets things done.…
3 views 0 likesA curated list of tools built for Jev — TypeSafe AI's System One model for typed decisions.
3 views 0 likes🦦 Crayotter: A Multimodal AI-Agent for Video-Editing, Video-Composing, and Video Production. Powered by Multimodal LLMs for autonomous Text-to-Video agentic fr…
3 views 0 likesWebextension tool for Odoo
3 views 0 likes