LLM Mart Basic
@llm-mart · Joined Jun 2026
The most important actions and content in a UI should be visually prominent — through size, colour, weight, and position. Visual hierarchy guides the user's eye to what matters most and signals which action is primary. Use when designing button groups, CTAs, dashboards, cards, or
UI must comply with WCAG 2.2 Level AA, as required by the European Accessibility Act (EN 301 549). Do not deviate without deliberate justification. Disabled UI elements are explicitly exempt from colour contrast requirements. Use when designing, building, or reviewing any user-fa
Install, observe, tune, and enforce Sponsio: a runtime contract layer for LLM agents that blocks unsafe tool calls and scores output quality against declared rules. Use when the user wants to set up / add / install Sponsio, add guardrails or runtime safety to an LLM agent, genera
Use after `/plugin install sponsio-claude-code` to wire the runtime end-to-end. The plugin install only registers hooks + skills; the contract library and per-environment overrides are configured here. Bootstraps the per-plugin contract library tree at ~/.sponsio/plugins/, instal
Use after installing the sponsio-openclaw plugin to wire the runtime end-to-end. The plugin install only registers hooks + skills; the contract library and per-environment overrides are configured here. Bootstraps the per-plugin contract library tree at ~/.sponsio/plugins/, gener
Install, observe, tune, and enforce Sponsio: a runtime contract layer for LLM agents that blocks unsafe tool calls and scores output quality against declared rules. Use when the user wants to set up / add / install Sponsio, add guardrails or runtime safety to an LLM agent, genera
Make a project ready for AI agentic engineering by converging it toward a canonical agent-neutral structure — a lean AGENTS.md index with progressive disclosure, shared skills and gitignore hygiene. Re-runnable, and doubles as an audit.
Check how much of a ticket is already implemented — split it into requirement blocks, judge each against the code, and save a human-readable TICKET-STATUS report in the planning dir.
Draft, rewrite, or refine a doc for maximum token economy without losing any rule or intent. Use for docs kept in version control and regularly re-read by agents; skip throwaway docs like plans.
Author or refine a skill for maximum token economy without losing intent. Use when creating any new skill or editing an existing `SKILL.md`.
Audit what auto-loads into an agent session's context window and suggest lean, reversible fixes to cut startup tokens.
Turn a refined requirements document into a structured implementation PLAN.md a fresh session can execute. Planning only — decides the "how", not the "what". Invoke manually only.
Turn a ticket or requirements document into a concise QA manual-test file a non-author can follow. Invoke manually only.
Execute one task from a plan's task breakdown, verify it, tick it off, and hand back for review before the next one.
Fetch all reviewer comments from a pull request URL (GitHub, Azure DevOps, …) and save them as a self-contained markdown PR-REVIEW file in the task's planning directory. Fetch only — no fixing or replying.
Fetch one or more tickets/issues from their tracker (Azure DevOps, Jira, GitHub, …) and save each as a self-contained markdown ticket file. Fetch only — no analysis or planning.
Fresh-eyes review of a changeset by a fresh-context agent — catches regressions and correctness issues the authoring context reads past.
Use when handing finished work over to code review — writing a PR description or packaging a change for review by a human, an agent, or both.
Review someone else's pull request as the maintainer deciding whether it merges — every prior comment walked, every claim verified, and nothing posted without your go-ahead.
Audit the current project's agent-memory and, block by block, relocate each entry into a user-controlled home (project doc/skill/rule or user-level skill/rule) or archive it — draining memory so nothing uncontrolled accumulates in the agent's context.
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
VCP 部署在 AI 模型 API 与前端应用之间,是面向AGI OS开发和探索的工业级基建示范项目。通过统一指令协议、多层级持久化记忆、分布式插件引擎及多 Agent 协作框架,将原本“无状态、无记忆、无工具调用能力”的大语言模型,彻底改造成拥有永久自我意识、物理世界操作权及群体协作智能的完整智能体系统。
2 views 0 likesThe open source Unity Dev Agent
5 views 0 likesContext is yours. Agents are replaceable. Orbital — a project agent that turns your context into assets.
1 views 0 likesSelf-hosted search API + MCP server for AI agents. Bundles SearXNG. Zero API keys, one-command deploy. Open-source alternative to Tavily, Exa, and Serper.
1 views 0 likes🛡️ Free open-source AI-powered security terminal & vulnerability scanner (CVE, SBOM). Supports SSH, SFTP, RDP, VNC, Serial, and 12+ autonomous AI agents (DeepS…
1 views 0 likesWatch, approve and steer your coding agents from your phone.
1 views 0 likesMARVIS-Agent: all-purpose credit risk agent for model development, validation, data processing, feature engineering, and strategy workflows.
1 views 0 likesTikTok e-commerce video generation, replication, and analysis SKILL
9 views 0 likes小红书/抖音/快手/视频号/B站 自媒体账号体检+爆款拆解工具。扫同赛道找对标、拆爆款为什么爆、诊断为什么没人看,顺手出可粘贴仿写初稿。支持带货电商模式。支持codex, claude code, workbuddy
7 views 0 likesLocal-first persistent agentic memory powered by Recursive Memory Harness (RMH). Open source must win.
3 views 0 likesA power user focused interface for LLM base models.
4 views 0 likesOutsource your understanding. Capture every human-AI decision as a step in a trajectory; grade trajectories retroactively when outcomes land (deal closed, sprin…
3 views 0 likesThe open-source AI research workbench for scientific research and agent workflows. Local-first, model-agnostic desktop app with extensible skills, MCP tools and…
4 views 0 likes🤖 Taskade MCP · Official MCP server and OpenAPI to MCP codegen. Build AI agent tools from any OpenAPI API and connect to Claude, Cursor, and more.
6 views 0 likesA block-based content engine and bilingual blog backend for Laravel Gutenberg-style editor, media library, post templates, roles, and an AI writing assistant,…
4 views 0 likesACRYL - Agent Context Relay Yielding Lifecycles. One persistent workspace, one canonical context, any coding agent.
3 views 0 likesOkou connects to the tools your team already uses and does the work — across marketing, sales, engineering, and operations, under your control.
4 views 0 likesOpen-source agent-native visual production workspace where humans and coding agents edit the same live canvas — local-first, BYOK image/video models.
1 views 0 likesPersistent memory extension for pi with daily logs, scratchpad, and optional qmd‑powered semantic search.
1 views 0 likesHermes Agent CN desktop app, Windows-First, built with Tauri, Typescript and Rust. Isolated Hermes Agent core insides.
2 views 0 likes