LLM Mart Basic
@llm-mart · Joined Jun 2026
Runs a grilling session that challenges a plan against the existing domain model, sharpens terminology, and updates the CONTEXT.md glossary inline as decisions are made. Use when the user wants to stress-test a plan against their project's language and documented decisions.
Compacts the current conversation into a handoff document another agent can pick up. Use when the user says 'handoff', 'hand off', or wants to continue this work in a fresh session.
Finds deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI
Read and write Jira work items through the acli CLI. Use when the user mentions a Jira ticket, issue, story, bug, or epic, drops a Jira key like SER-123, or pastes an atlassian.net/browse URL.
Create a merge request or pull request from the current branch: verify quality gates, enforce conventional commits, validate the title, and create it without a confirmation step. Use when the user says 'create MR', 'create PR', 'open a merge request', or 'raise a PR'.
Builds a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
Reviews code exclusively for over-engineering and lists what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. Use when the user says 'review for over-engineering', 'is this over-engineered', or invokes /prune. Complements
Starts Phase 1 (Research) for a topic: reads every relevant file, optionally runs a panel of Explore teammates, and saves a research artifact to .claude/state/research/. Use when the user says 'research <topic>' or '/research', or before planning work in unfamiliar code. Research
Reviews a pull request with structured severity-based feedback. Use when asked to review a PR, asked for a code review, or given a PR number/URL.
Fetches and digests Sentry issue data (summary, tags, stack trace, breadcrumbs, latest event) by short ID, numeric issue ID, or sentry.io URL, for any Sentry org the local token can access. Use when the user mentions a Sentry issue or short ID (e.g. MY-PROJECT-4X2), pastes a sent
Runs pre-launch validation and the release workflow. Use when the user says 'ship', 'release', 'deploy', or 'ready to merge'.
Summarizes the current session's work into a diary entry at .claude/state/sessions/ and runs worktree auto-cleanup. Use when the user says 'summarize' or '/summarize', or when closing out a completed work session.
Breaks a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when the user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
Runs the comprehensive quality gate before declaring work done: discovers the checks CI actually runs, executes them in order, then reviews git status and the session diff. Use when the user says 'verify done' or '/verify-done', or before pushing any branch.
Plans a huge chunk of work - more than one agent session can hold - as a shared map of decision tickets in a local file, and resolves them one at a time until the way to the destination is clear. Use when the user invokes /wayfinder on an effort too big for a single session.
Creates an isolated git worktree for the current task and switches into it, so the task never collides with the main checkout. Use when the user says '/worktree <slug>' or wants an isolated working copy for a new task.
Cleans up a worktree after its branch has been merged: removes the worktree directory and deletes the local branch. Use when the user says '/worktree-merge' or asks to clean up a merged worktree.
Audits and optionally prunes git worktrees: current repo by default, cross-repo scan under ~/dev/ with --all. Use when the user says '/worktrees', 'audit worktrees', or 'prune worktrees'.
Provides the reference and principles for writing and editing skills well - the vocabulary that makes a skill predictable. Use when creating, writing, editing, reviewing, or refactoring an agent skill.
Designs and reviews ArgoCD Applications, ApplicationSets, AppProjects, sync policies, and Argo Rollouts progressive delivery. Use when the task involves ArgoCD manifests, sync behavior, GitOps repo layout, or canary/blue-green rollouts. General Kubernetes and CI pipeline work bel
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.
/health
Health
One-line reliability verdict (OK / DEGRADED / FAILING) for Claude Code usage
/slo
Slo
Print a quick SLO snapshot — completion rate, tool success rate, and error rate
/report
Report
Generate an evidence-backed CCAM executive, cost, reliability, or workflow report.
/runs
Runs
List live and persisted CCAM-launched Claude Code and Codex runs
/find-session
Find session
Search Agent Monitor sessions by cwd, model, or status and print the top matches.
/recent
Recent
List the N most recent Claude Code sessions from the Agent Monitor.
/replay
Replay
Summarize one Agent Monitor session by id — header plus a concise transcript recap.
/dag
Dag
Print the orchestration DAG edges (parent→child subagents) for a session.
/runs
Runs
List recent Workflow-tool fleet runs with status and agent counts.
/workflow
Workflow
Summarize the workflow intelligence for a session — stats, complexity, and top patterns.
/broadcast
broadcast
Run broadcast on a distilled Raw — update related existing pages conversationally
/distill
distill
Distill raw session records into refined Notes and Projects
/evolve
evolve
Save knowledge to the cortex vault (Notes or Projects) and update index
/genesis
genesis
Initialize cortex vault — set up config, vault structure, and rebuild index
/query
query
Manually search the cortex vault (Notes, Projects, Raw) for existing notes
/takeoff
takeoff
Create, resume, or clear a session hand-off baton (one per work line)
/dev
Dev
Command → Agent → Skill orchestration for end-to-end feature development.
/investigate
Investigate
Command → Agent → Skill orchestration for investigating and fixing bugs.
/company
Company
Brief the CEO: coordinate with the peer CTO and start or resume a founder project across 8 departments and 54 skills
/onboard
Onboard
Configure an optional active team profile in three short questions
Your Personal AI Assistant; easy to install, deploy on your own machine or on the cloud; supports multiple chat apps with easily extensible capabilities.
16 views 0 likesAgent OS: the agent gets smarter on its own. We just hold the line: the grading command and expected result never make it into the success contract we hand it.…
17 views 0 likesCurated systems, benchmarks, and papers etc. on memory for LLMs/MLLMs --- long-term context, retrieval, and reasoning.
14 views 0 likes:memo: Vimlike Modal Text Editor in Rust
27 views 0 likesCI-native security testing for MCP servers. Attack simulation, schema drift detection, and health scoring before agents depend on them.
16 views 0 likesHermes Agent memory plugin/provider for scope-aware recall, SQLite truth, LanceDB semantic search, and hybrid retrieval.
15 views 0 likesFor You Agent——AI 时代的个人随身数字人格。把你的模型、AI 账号、技能、提示词和工作方式,带到每一个 AI 工具里。
12 views 0 likesA coding agent: give it a prompt and it reads, writes, runs commands, and searches code in a loop until the work is done, using native tool-calling across OpenA…
14 views 0 likesA secure persistent personal agent server in Rust. One binary, sandboxed execution, multi-provider LLMs, voice, memory, Telegram, WhatsApp, Discord, Teams, and…
14 views 0 likesSelf-evolving agent: grows skill tree from 3.3K-line seed, achieving full system control with 6x less token consumption
14 views 0 likesDeepSeek Harness Desktop (dsh-desktop). EAC: Embracing All Creation (揽尽万象). Bundled Node.js runtime with full dsh-CLI kernel, one-click startup, 10 built-in UI…
14 views 0 likesSee your agent think. Zero-config observability & governance for 26 AI agent runtimes: Claude Code, Cursor, OpenAI Codex, GitHub Copilot, Gemini CLI, Cline, Ope…
13 views 0 likesSave 94% on AI coding tokens. Index your codebase, agents search instead of reading files. Works with Claude Code, Codex, Copilot, Cursor, Gemini CLI. Local MCP…
12 views 0 likesYet another coding agent harness, lightweight and written in go.
12 views 0 likesa coding Agent from pi. ∞ providers, sub-agents, hashline edits, and a permission gate
12 views 0 likesOmnigent is an open-source AI agent framework and meta-harness: orchestrate Claude Code, Codex, Cursor, Pi, and custom agents — swap harnesses without rewriting…
25 views 0 likes🧠 Leon is your open-source personal assistant.
12 views 0 likesThe Station, an open-world multi-agent environment that models a miniature scientific ecosystem.
14 views 0 likesThe Frontend Stack for Agents & Generative UI. React, Angular, Mobile, Slack, and more. Makers of the AG-UI Protocol
23 views 0 likesVelaTerm = iTerm2 + Codex, The Best Terminal for AI Coding
21 views 0 likes