LLM Mart Basic
@llm-mart · Joined Jun 2026
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.
/liongard-environment-summary
Liongard environment summary
Generate a detailed summary of a Liongard environment
/liongard-health-check
Liongard health check
Check Liongard connectivity and return system health summary
/check-mfa-status
Check mfa status
Audit MFA enrollment across all M365 users, highlighting accounts with no MFA
/get-user
Get user
Look up a Microsoft 365 user by name or email, showing account status, licenses, MFA, and last sign-in
/list-licenses
List licenses
Show Microsoft 365 license inventory - available SKUs, consumed seats, and optimization opportunities
/offboard-user
Offboard user
Run the complete M365 offboarding workflow for a departing user - revoke access, handle mailbox, transfer data
/block-sender
Block sender
Create a Mailprotector block rule for a sender address or domain at a chosen scope
/check-quarantine
Check quarantine
Review the Mailprotector quarantine at any scope and summarize held messages
/onboard-customer
Onboard customer
Onboard a new customer onto Mailprotector - customer, domain, user group, services, users
/release-message
Release message
Release one or more quarantined Mailprotector messages to their recipients
/meraki-find-device
Meraki find device
Locate a Meraki device by serial, name, or MAC across an organization's networks
/meraki-firewall-review
Meraki firewall review
Pull and summarize a Meraki network's L3 firewall rules and flag overly-permissive (any/any allow) rules
/meraki-network-health
Meraki network health
Sweep an organization's networks, devices, and appliance VPN status for a site-health overview
/entra-audit
Entra audit
Run a read-only Microsoft Entra identity hygiene audit via the Graph Enterprise MCP — inactive user accounts, admins without MFA registered, unassigned/wasted licenses, and a guest user inventory
/entra-report
Entra report
Conversational Microsoft Entra directory reporting via the Graph Enterprise MCP — license usage, user and group counts, application inventory, and directory composition, formatted for client check-ins and QBRs
/check-queue
Check queue
Check Mimecast email delivery queue status and identify stuck or deferred messages
/review-threats
Review threats
Review Mimecast TTP threat logs for URL clicks, malicious attachments, and impersonation attempts
/trace-message
Trace message
Trace an email through Mimecast by sender, recipient, subject, or date range
/device-inventory
Device inventory
Inventory devices for an N-central customer or site with class, warranty, and monitor-health breakdown
/issue-sweep
Issue sweep
Sweep active issues across N-central customers, grouped by severity and probable root cause
The fastest way to put Volcengine Ark in your terminal and your AI agent — go from prompt to generated media, multimodal answer, or deployed endpoint in a sin…
12 views 0 likes本地私有、开源的自进化跨平台 AI 内容发现 Agent:先理解你,再主动从 B站、小红书、抖音、YouTube、X、知乎、Reddit、微博等平台与开放 Web 寻找内容。(支持 deepseek harness 插件) | Local-first open-source cross-platform AI cont…
14 views 0 likesPersistent memory for AI coding agents — one verified kb_search replaces the grep/find/ls orientation loop. Cross-repo, CPU-only, zero token spend.
14 views 0 likesAI 时代的伯克希尔:基于 Claude Code / Codex 的价值投资研究框架。巴菲特·芒格·段永平·李录四大师方法论 + 多Agent并行研究。| AI-era Berkshire: a value investing research framework built for Claude Code / Co…
14 views 0 likesThe batteries-included, No-Code FinOps automation platform, with the AI you trust.
15 views 0 likesOpen-source 3D AI agent framework — GLB/glTF avatars with LLM brains, memory, emotions, and autonomous payments. MCP server · x402 · Solana/EVM · Three.js. Embe…
27 views 0 likesXLSX parser for LLMs, RAG, LangChain, LangGraph, CrewAI, Claude, MCP — turns Excel (.xlsx) into citation-ready JSON with formulas, charts, dependency graphs, an…
25 views 0 likesHermes-Relay — Your Hermes AI agent, in your pocket — chat, voice, and control.
15 views 0 likesA minimalist, terminal-native coding agent written in C.
14 views 0 likesAI-powered OSINT agent with interactive REPL, MCP server, and CLI. 19 tools. Works with Claude, GPT-4, or local models. For authorized security research only.
12 views 0 likesAI pair programming in your terminal — one static binary, sub-ms startup, any model
12 views 0 likesWhere data access meets operational intelligence
12 views 0 likesBuild your own security agents. Open-source framework for agents with live, read-only access to your infrastructure, with no path to widen it. Reasons across AW…
12 views 0 likesMulti-workspace terminal aggregator with Claude Code AI integration
16 views 0 likesGo implementation of AI coding agent
14 views 0 likesHarness engineering beginner tutorial, from 0 to 1
15 views 0 likesGenerate images directly in DeepSeek Harness chats
27 views 0 likesA smarter, self-hosted AI assistant — multi-user, multi-agent.
16 views 0 likesTurn any research paper into a commercialization report — 6 AI agents, TRL/MRL scoring, patent landscape, market intelligence, verified citations. DeepSeek / Op…
15 views 0 likesPower BI CLI - semantic models (.NET TOM) and PBIR reports for token-efficient AI agent usage, built for Claude Code
15 views 0 likes