LLM Mart Basic
@llm-mart · Joined Jun 2026
Use when an Agent needs to capture, find, update, finish, cancel, or reopen durable deferred work in LWC.
Use for explicit teacher-led learning, an active Tutor session, or recovery of pending Tutor work. Skip ordinary factual questions.
Use to import, prepare, read, or synthesize a complete supported book in verified source order. Skip ordinary document lookup.
Use when substantive project work, structural code questions, research, planning, debugging, architecture, decisions, document ingest, incident recovery, or verified context and results should survive future sessions; also when the user invokes $using-lwc or asks to search, updat
Use when an Agent needs to create, resume, advance, block, revise, complete, or abandon a durable current execution plan in LWC.
Use for durable questions, banks, papers, attempts, grading, flashcards, or scheduled review. Skip disposable one-off questions.
Use when an Agent needs to synchronize LWC Wiki stores across SSH hosts, resume or abort an interrupted Sync session, or resolve semantic Sync conflicts safely.
Use when an Agent needs to capture, find, update, finish, cancel, or reopen durable deferred work in LWC.
Use for explicit teacher-led learning, an active Tutor session, or recovery of pending Tutor work. Skip ordinary factual questions.
The Socratic spec-refinement front of /feature, and the planning front of /sprint. Routed to BEFORE any code — it takes a one-line idea and drives it to an approved, concrete spec with testable acceptance criteria. Five gated phases — frame, shape, refine, write, review-and-appro
The only path to a commit. Routed to when the user invokes /commit or otherwise instructs codeArbiter to persist staged changes. Nine gated phases — permission, branch, classification, verification (test/lint/secrets), behavioral proof, diff review, selective stage, message, comm
Optional manual drift audit — report stale provenance-tracked docs (via _provenancelib drift detection across .codearbiter/.provenance/), then per stale doc offer re-scout / re-baseline / defer. Not the daily loop; commit-gate auto-heal owns routine maintenance.
The brownfield back-fill. Routed to by /create-context, and by startup when .codearbiter/CONTEXT.md lacks the <!--INITIALIZED--> body marker but source code exists. Six gated phases — pre-flight, scout dispatch, synthesis, gap interview, write, lock. Reads the existing codebase t
The banned-primitive gate. Routed to when changed code hashes, signs, encrypts, derives keys, generates security-relevant randomness, configures TLS, or imports a crypto library. Rejects broken primitives, disabled TLS verification, and home-rolled crypto; the approved-primitive
Investigate-then-decide root-cause analysis for a defect whose cause is unknown (distinct from /fix, which assumes a known bug). Five gated phases: capture, hypothesize, gather, decide, hand off. Investigation only, no code changes; exits to /fix, /adr, or a no-action close.
Author and track Architecture Decision Records. Routed to when the user invokes /adr to record a new decision or /adr-status to list ADR health. Authors numbered, dated, user-attributed ADRs under .codearbiter/decisions/, maintains supersede chains, and reports status read-only.
Reconcile the project's architectural artifacts against the scaffold and prior decisions, then present each variance as a SMARTS analysis for the user to decide. Routed to when the user asks to arbitrate, reconcile, or consolidate architectural context, requests a variance report
The greenfield decomposition interview. Routed to at startup when .codearbiter/CONTEXT.md lacks the <!--INITIALIZED--> body marker and no source code exists, or when the user invokes /decompose. A senior-architect persona drives a six-layer interview, persists every layer to disk
The parallel fan-out primitive. Routed to by any skill or command that splits work across independent units and dispatches an agent per unit — subagent-driven-development, /sprint, parallel /review. It owns the dispatch/collect/funnel discipline: bound concurrency, isolate units,
The checkpoint coordinator for /feature. Routed to by /feature once a writing-plans plan exists. Groups tasks into batches, delegates each batch to subagent-driven-development (fresh author agent per task, full review chain, fresh verification), then stops for a human checkpoint
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
AI coding platform for teams
20 views 0 likesAI Multi-Agent Framework in .NET
14 views 0 likesProduction-ready code examples for Telnyx AI Communications Infrastructure — Voice AI, SMS, SIP, and IoT APIs
12 views 0 likesUltraGameStudio - AI coding agent for game development: engine workflows, gameplay code, and asset generation.
12 views 0 likes🦞 ResearchClawBench: Evaluating AI Agents for Automated Research from Re-Discovery to New-Discovery
12 views 0 likesThe context-aware model router that learns & adapts to your long-horizon coding agent workflows. Lightweight & extensible, works with any harnesses, any models,…
20 views 0 likesOpen-source sandboxes where coding agents build and deploy. Spin up isolated environments where Claude Code, Cursor, and other agents code and deploy software.
24 views 0 likesNative desktop UI for Claude Code with orchestration, streaming, background agents, and multi-provider support. Built with Tauri + React.
22 views 0 likesOpenCode mobile client via Telegram: run and monitor AI coding tasks from your phone while everything runs locally on your machine. Scheduled tasks support.
17 views 0 likesTerminal session manager for AI coding agents. One TUI for Claude, Gemini, OpenCode, Codex, and more.
23 views 0 likesExposes internet search tools for use by LLM-backed Assist in Home Assistant
15 views 0 likesTemplates and workflow for generating PRDs, Tech Designs, and MVP and more using LLMs for AI IDEs
8 views 0 likesVersus Incident is the self-hosted AI SRE agent. It learns what your system normally look like and escalates only what is new or unexpected issues — routing to…
14 views 0 likesBrowser-native side panel for Hermes Agent — connect web context to your local Hermes runtime.
6 views 0 likesAgentic-friendly CLI generator for APIs: turn Swagger, OpenAPI, and google.api.http protos into single-binary CLIs with catalogs and generated Skills.
10 views 0 likesOpen-source agent platform for Global × China enterprises — wire every system through one agent core. Self-hosted, any LLM.
7 views 0 likesOfficial python implementation of UTCP. UTCP is an open standard that lets AI agents call any API directly, without extra middleware.
11 views 0 likesAn agent small enough to run anywhere. A minimal agentic runtime in C — ~380 lines, 54KB binary, ~2MB RAM. A skill file + an LLM + a shell loop, no framework.
10 views 0 likesAgentiLoop Agent! An Autonomous Agentic Agent for Mac, and exclusive Apple only harnesss. Suppprtd automation, scripting, coding, build anything and more. Power…
10 views 0 likes微信公众号 AI 运营助手 | 选题、写稿、审稿、排版、配图、发布全流程 Skill,支持 OpenClaw / Claude Code / Cursor / Codex
17 views 0 likes