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.
/lookup-config
Lookup config
Search for configuration items (assets) in ConnectWise PSA
/schedule-entry
Schedule entry
Create a schedule entry/appointment in ConnectWise PSA
/search-tickets
Search tickets
Search for tickets in ConnectWise PSA by various criteria
/update-ticket
Update ticket
Update fields on an existing ConnectWise PSA ticket
/search-surveys
Search surveys
Search recent Crewhu surveys, surfacing detractors and promoters
/error-budget
Error budget
Run the reliability scorecard for one service, or every connected service if omitted - error-budget burn rate where an SLO is defined, trend reporting otherwise
/oncall-brief
Oncall brief
Generate the current on-call handoff brief - what's paging, what's escalated without an owner, last-shift history, and known-flaky alerts to watch
/postmortem
Postmortem
Draft a blameless postmortem for a given incident (by ID or name), or the most recent significant incident within a time window
/device-inventory
Device inventory
List all devices at a Domotz-monitored site
/device-lookup
Device lookup
Find a Domotz device by name, IP address, or MAC address
/site-overview
Site overview
Overview of a Domotz site's network health
/check-threat
Check threat
Pull full detail for one Checkpoint Harmony Email detection and the message behind it
/release-quarantine
Release quarantine
Restore quarantined mail to its recipients in Checkpoint Harmony Email, with task polling
/search-quarantine
Search quarantine
Find messages in Checkpoint Harmony Email by sender, subject, attachment hash or quarantine state
/search-threats
Search threats
Sweep security events in Checkpoint Harmony Email by type, state, severity and date range
/campaign-summary
Campaign summary
Get summary of recent phishing and training campaigns from KnowBe4
/group-report
Group report
Get security awareness metrics for a KnowBe4 group
/phishing-results
Phishing results
View phishing campaign results and click rates from KnowBe4
/training-status
Training status
Check training completion status for users or groups in KnowBe4
/user-risk
User risk
Get risk score and risk history for a KnowBe4 user
Persistent session memory for AI coding agents — local-first, with on-device inference, associative recall, and drift detection. Works with Claude Code, Cursor,…
12 views 0 likesRun Hermes Agent and OpenClaw on the same WeChat account
12 views 0 likesAn AI co-scientist running on your desktop. Claude Science but better.
12 views 0 likesEmotion Ball 是一套面向 AI 助手的表情引擎:32 种状态表情全部由纯 SVG 与原生 JavaScript 实时驱动,零框架、零图片资源。AI 侧只需输出一个 emotionId,小球即可切换到对应表情,可直接用作聊天机器人、桌面宠物、悬浮助手的情绪表达层。
14 views 0 likesAgent communication SDK. The open-source agent communication layer for AI agents — email, WhatsApp, Slack, Discord, Telegram, SMS. Python & TypeScript.
16 views 0 likesThe micro-VM for AI agents — light enough to embed on your laptop, elastic enough to power an agentic cloud.
23 views 0 likesGive each AI agent its own isolated machine with root, Docker, and systemd. Active defense detects and stops threats automatically.
14 views 0 likesWebhook integration skills for AI coding agents (Claude Code, Cursor, Copilot). Step-by-step guidance for setting up webhook receivers, signature verification,…
16 views 0 likesToken burn reducer and focus keeper for Claude Code, Codex, Copilot, Gemini CLI, and more: surgical read hints, PDF/Office/CSV/markdown file interception, 160+…
16 views 0 likesRuvNet Brain — a downloadable, source-grounded brain for Claude Code over Reuven Cohen's (rUv's) RuvNet stack: RuVector/RVF, Ruflo, AgentDB, RuLake, SPARC + 21…
16 views 0 likes💼 One MCP server to search job boards and company career sites
14 views 0 likesC++ MCP SDK - build Model Context Protocol (MCP) servers and clients in C++ / CPP. Enterprise-grade security, observability, connectivity. Stdio, HTTP+SSE, Stre…
12 views 0 likesOpen-Source AI Presentation Generator and API (Gamma, Canva, Beautiful AI, Decktopus, Presentations AI Alternative)
14 views 0 likesSecure, Fast, and Extensible Sandbox runtime for AI agents.
28 views 0 likesGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
12 views 0 likesBrowser Harness | Self-healing harness that enables LLMs to complete any task.
12 views 0 likesThe World's First Agentic IDE. Visual dashboard: live sessions, task management, code editor, terminal. Epic Swarm parallel workflows. Auto-proceed rules. Autom…
15 views 0 likesAgenta is a workspace where you and your team build agents and automations.
16 views 0 likesTerminal Director. One lightweight app, eight features, your whole dev workflow in a single window.
15 views 0 likesAI turns documents or topics into real, native PowerPoint decks—with native shapes, transitions and animations, data-backed charts and tables on demand, audio n…
13 views 0 likes