LLM Mart Basic
@llm-mart · Joined Jun 2026
Read a detached Codex bridge job's current state.
Ask Claude Code a read-only question from Codex through the sandbox-external bridge.
Ask Claude Code to implement one bounded write-capable change through the sandbox-external bridge.
Request a read-only adversarial review from Claude Code through the sandbox-external bridge.
Configure, authenticate, repair, and verify the Codex to Claude Code Bridge; safe stages run by default and sensitive stages require separate approval.
Safely manage Codex Rig role-agent shims: doctor, status, install, or remove; one action only.
Audit Codex configuration, workflow, and prompt-efficiency (instruction cost, value-per-token) drift; emit ranked gaps and measurable gates.
Calibrate skills/role cards for leaks/gaps with recall, precision, and confidence-accuracy checks.
Apply selected review fixes; bare PR targets use current online items, while PR +review adds the latest matching artifact.
Close PRs at an evidence gate or review local diffs/PRs with specialists and JSON artifacts.
Implement changes with a linear plan-build-verify workflow and measurable quality gates.
Investigate code debugging and root-cause narrowing; use measurable gates before fixes.
Build/extend grounded Kaggle Jupytext notebooks for training, EDA, inference, or resume workflows, grounding schema and submission format through the authenticated kaggle CLI.
Optimize a measurable metric with bounded iterations, guardrails, and regression gates.
Assess SemVer release readiness with gates/artifacts; never tag, publish, upload, or force-push.
Research docs, papers, or state of the art; provide source-backed recommendations and caveats.
Dry-run active plugin cache drift; refresh/reinstall only with approval; keep shims separate.
Adversarial review — drills to bedrock, treats claims as unproven until evidence. NOT for: plan design (foundry:solution-architect), test coverage (foundry:qa-specialist), config formatting (foundry:curator). TRIGGER: "challenge this", "devil's advocate", "poke holes in". SKIP: w
Content specialist — blog posts, slide decks, social threads, talk abstracts. Reads approved outline, applies four-beat arc. NOT for in-code docs/README/FAQs (foundry:doc-scribe), release notes (oss:release). TRIGGER: "write a blog post", "create slides", "draft a thread". SKIP:
Config quality reviewer. Scope: agents/skills/rules (*.md) — verbosity, duplication, cross-refs, roster overlap; applies fixes. NOT for hooks (foundry:sw-engineer), ADRs (foundry:solution-architect), adversarial challenge (foundry:challenger). TRIGGER: "audit this agent", "review
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.
/afst
Afst
Show current AutoFile policy and settings
/allow
Allow
Allow all file creation - full permission to create and modify files
/autoproc
Autoproc
Start autoproc - procedural autonomous workflow (legacy command)
/autorun
Autorun
Start autorun - autonomous task execution (legacy command)
/blocks
Blocks
Show active session-level pattern blocks and allows
/cache
Cache
Cache-miss / compaction protection gate (disabled by default)
/claude-code-plugin-help
Claude code plugin help
Reference the supported Claude Code command, skill, plugin, and hook surfaces
/clear
Clear
Clear all session-level pattern blocks and allows
/estop
Estop
Emergency stop - immediately halt all autonomous operations
/f
F
Find existing files only - no new file creation (short for /ar:find)
/find
Find
Find existing files only - prevents new file creation (strictest mode)
/gc
Gc
Git commit requirements - the 17-step process, short for /ar:commit
/gemini
gemini
Use gemini CLI for any combination of: superior vision for analysis of images, diagrams, screenshots, PDFs, documents, video, and audio; code review with detailed citations and cross-referencing patterns; Google search; and multi-model workflows; all for planning, feedback, and getting unstuck.
/globalclear
Globalclear
Clear all global pattern blocks and allows
/globalno
Globalno
Block a command pattern globally (persists across sessions)
/globalok
Globalok
Allow a blocked pattern globally (persists across sessions)
/globalstatus
Globalstatus
Show active global pattern blocks and allows
/go
Go
Start autorun - autonomous task execution (short for /ar:run)
/gp
Gp
Start autoproc - procedural autonomous workflow (short for /ar:proc)
/help
Help
List every autorun command with what it does, in this harness's spelling
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