LLM Mart Basic
@llm-mart · Joined Jun 2026
Use when evaluating Carbon for a C++ code base, running the carbon toolchain from a nightly or Bazel build, or comparing Carbon with staying on C++. Not for C++ modules: use cpp-modules.
Use when initializing, running, measuring coverage, or triaging a cargo-fuzz target in a Rust crate. Not for remote, credential, publish, deploy, or irreversible changes.
Use when managing Cargo workspaces, feature flags, build scripts, CI caching, dependency auditing, or Cargo.lock with Rust.
Use when prompt-doctrine is duplicated, drifted, or conflicting across output-style embeds and external harness AGENTS files. Not for editing the canonical baseline itself.
Use when the human returns after a gap, cannot follow the project, asks what happened, or wants a visual HTML recap page. Not for onboarding: use onboard. Not for handoff: use handoff.
Use when an Algorand, Cairo, Cosmos SDK, Solana, Substrate, or TON codebase needs vulnerability scanning with reachability-backed findings. Not for non-chain review: use security-review.
Use when a release or a since-tag window needs user-facing release notes drafted. Not for publishing the release.
Use when a human explicitly asks for a full repository agent-compatibility pass returning a scored report with prioritized fixes. Not for tasks that require source or remote-system changes.
Use when the user asks to cherry-pick, backport, or apply a hotfix to a release branch. Not for merging feature branches or cutting new release branches.
Use when the user explicitly asks to build, modify, or publish a Manifest V3 Chrome extension. Not for store submission without human-gated credentials.
Use when setting up or modifying CI/CD pipelines, quality gates, test runners, or deployment pipeline configuration through workflow files. Not for triggering a deployment.
Use when "CI is red", "fix the checks", or "make CI green", one check needs classifying, or a bounded sweep runs. Not for deploys, credentials, or rerun-as-fix. Non-CI bugs: use strike-the-root.
Use when a C or C++ build uses clang and needs diagnostics, optimization remarks, clang-tidy, ThinLTO with lld, LLVM PGO, or a GCC-to-Clang migration. Not for LLVM IR work: use llvm.
Use when setting up a project, auditing agent command permissions, or asking which read-only bash commands and domains to allow. Not for remote, credential, publish, deploy, or irreversible changes.
Use when the user just edited a durable artifact, or says "clean and true", "run the hygiene pass", or "taste the output". Routes the artifact through the hygiene passes it earned.
Use when asked to run /clean-clean-cut to cut accumulated records and residue. Not for untracked or non-VCS changes, or branch/worktree cleanup: use git-cleanup.
Use when asked to build or review a CLI intended for coding agents and return flag-driven, pipeline-safe, idempotent design advice. Not for running or profiling a CLI: use control-cli.
Use when the user wants to batch-close resolved or outdated tracker items. The agent never closes tracker items itself. Not for individual closure or items still under active work.
Use when a human explicitly runs /cloud-task-orchestrator for a large task across cloud agents to drain a verified task graph. Not for local subagent coordination: use orchestration-patterns.
Use when writing CMakeLists.txt, out-of-source builds, target_link_libraries, target properties, find_package/FetchContent, toolchain files, CPack, CMake presets, or cmake configure errors.
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.
/bloat-scan
bloat-scan
Scan for codebase bloat using 3-tier progressive analysis: dead code, duplication, God classes, and documentation waste.
/elegant-code-review
elegant-code-review
Review the current working diff against the elegant-code decision ladder and propose deletions, honoring the negligence floor.
/filter-log
filter-log
Suggest tier-1 filter commands for a log file before any compression or paste. Anchors on the log-debugging-hygiene module.
/optimize-context
optimize-context
Analyze and optimize context window usage using MECW principles
/unbloat
unbloat
Remove dead code, duplicate files, and unused dependencies with user approval at each step. Backs up before deleting.
/dismiss
dismiss
The ONLY way to stop the egregore. Human-initiated graceful shutdown that saves all state.
/install-watchdog
install-watchdog
Install the egregore watchdog daemon for automatic session relaunching
/status
status
Show current egregore state and progress
/summon
summon
Summon the egregore to autonomously process work items through the full development lifecycle. Runs indefinitely by default until dismissed.
/uninstall-watchdog
uninstall-watchdog
Remove the egregore watchdog daemon and clean up files
/gauntlet-curate
Gauntlet curate
Add or edit a knowledge annotation
/gauntlet-extract
Gauntlet extract
Rebuild the knowledge base from the current codebase
/gauntlet-graph
gauntlet-graph
Build, search, and query the code knowledge graph
/gauntlet-onboard
Gauntlet onboard
Start or resume a guided onboarding path
/gauntlet-progress
Gauntlet progress
Show challenge accuracy stats, weak areas, and streak
/gauntlet
Gauntlet
Run an ad-hoc gauntlet challenge session (5 questions, random scope)
/configure
configure
Interactive interface to enable/disable rules
/from-hook
from-hook
Convert Python SDK hooks to declarative rules
/help
help
Display help and documentation
/hookify
hookify
Create behavioral rules to prevent unwanted actions
Your efficient agentic AI coding CLI assistant
2 views 0 likesAI coding with Aegis governance built into execution: baseline-aware changes, evidence-backed delivery. Free desktop client, your choice of model. 将哲科思维融入 AI 开发…
1 views 0 likesAndroid in docker solution with noVNC supported, video recording, mcp server and AI-agent
2 views 0 likesYour AI assistant, built for the agentic era. Open source and local: talk to it, and it runs your agents, your coding CLIs, your browser and your apps. Windows,…
0 views 0 likesVerifiable program-level self-evolution for AI-for-Science agents: Skills and typed Operators grow from replay-verified executions.
3 views 0 likesLet Claude Code and other coding agents drive and debug Chrome from the shell. DOM, network, console and raw CDP as short commands, no screenshots and no MCP ne…
3 views 0 likesUnofficial, agent-friendly Mercadona shopping CLI (Go) — search products, read prices, build a cart and prepare checkout from the terminal. BYO credentials.
3 views 0 likesLocal-first AI canvas for visual workflows, AI short drama, image/video generation, storyboarding and asset management. ComfyUI, AI agents, MCP & Blender. 本地优先…
3 views 0 likesLet any AI coding tool — Claude Code, Cursor, Codex — drive your real Chrome. One-prompt setup, muscle memory, local-first.
3 views 0 likesruns anywhere. uses anything
3 views 0 likesOpen-source dots for the web: an AI agent with its own browser, one that does not get blocked.
0 views 0 likesFree MIT AI coding agent — no API key needed. Built-in free model, or bring Claude, GPT, Gemini, DeepSeek, Ollama +50 more. Swarm mode, 40+ tools, browser & des…
3 views 0 likesOpen-source AI customer support system. AI-first support, human-ready operations.
2 views 0 likesA durable, multiplayer, mobile-first web app for Pi agents, built on Pi Durable
3 views 0 likesEmbedded Cypher knowledge graph for Python and Rust. Bundled MCP server, describe() schema, and code-graph parser for LLM agents.
3 views 0 likesTurn PDFs, books and papers into interactive learning webpages|将复杂材料转化为可追溯、可测验、可做笔记的学习网页
2 views 0 likesPhysicsOS 是一个面向初高中物理学习的公益可视化智能体,通过 AI 理解题目并结合物理引擎,将抽象物理过程转化为可交互、可观察、可计算、可验证的真实物理场景。
3 views 0 likes