LLM Mart Basic
@llm-mart · Joined Jun 2026
Token-isolated deep research agent for academic papers. Orchestrates Exa MCP (neural multi-source discovery), allenai's semantic-scholar-lookup skill (fast metadata + forward citations via asta CLI), and the semantic-scholar-deep skill (references, recommendations, batch, citatio
Turn any AI agent into an AI Scientist. The #1 Agent Skills library for science, used by 190,000+ scientists worldwide. 165 ready-to-use validated skills plus 1…
Work with a local My Wiki knowledge base, Dashboard, and knowledge graph. Also use for explicitly requested remote/public knowledge access, including “远程知识库”, “远程服务”, “公网知识库”, and “公网服务”.
Use when touching retiring old logic, collapsing duplicate owners, removing fallbacks, or schema/persistence/source-of-truth boundaries; identify opportunities automatically; destructive execution requires explicit confirmation.
Use when defining ambiguous or high-complexity new features, product behavior, UI/component design, architecture choices, contract changes, or when grilling/pressure-testing a plan or design. Routine small requests stay on the fast path.
Use when the user asks for caveman mode, fewer tokens, brief responses, compressed communication, or otherwise explicitly requests a much shorter answer.
Use when facing 2+ independent tasks without a written plan, with no shared state or sequential dependencies, where parallel delegation beats inline cost; otherwise inline. Planned tasks use subagent-driven-development.
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
Use when executing a written implementation plan across sessions or with review checkpoints. Small or single-slice plans stay inline. For same-session independent tasks, use subagent-driven-development instead.
Use when verified work needs integration or cleanup of an existing task-created branch/worktree, or the user explicitly requests merge, PR, or branch lifecycle handling.
Use when asked for first-principles or Occam's-razor review, or when high-risk decisions involve competing constraints, fallback growth, duplicate owners, or architecture direction risk. Ordinary bug fixes stay on the fast path.
Use when the user explicitly sets an Aegis goal with /aegis-goal, Aegis goal:, or asks to define goal, success evidence, stop condition, or task boundaries before work.
Use when a task is multi-step, may span context resets or sessions, uses subagents, or risks losing state before completion.
Use when receiving code review feedback before implementing suggestions, especially when feedback is unclear, risky, disputed, or technically questionable.
Use when the user asks to create, write, update, amend, supersede, or evaluate an ADR, architecture decision record, durable architecture decision, decision log, or baseline sync after architecture-changing work.
Use when requesting independent code review, after implementation slices, before merging high-risk work, or when verification exposes evidence, baseline, architecture, compatibility, or retirement uncertainty.
Use when executing a written implementation plan with independent tasks in the current session where delegation beats inline coordination cost; otherwise inline. Ad-hoc 2+ tasks without a plan use dispatching-parallel-agents.
Use when encountering a bug, test failure, or unexpected behavior, before proposing fixes
Use when the user explicitly requests strict or test-first TDD, or when the current conversation already contains an explicit `TDD Route: strict` decision from another Aegis workflow.
Use when the user says `aegis:update`, asks to update or upgrade an installed Aegis method-pack, wants the latest Aegis version, or asks whether Aegis is current on this host.
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.
/proposal
Proposal
Create a multi-page funding proposal with your organization's branding
/report
Report
Create a program report or annual report with your organization's branding
/slides
Slides
Create HTML presentation slides with your organization's branding
/update
Update
Check for updates and install the latest version
/hotpatch
Hotpatch
Sandboxed pre-install scan plus cooldown bypass for urgent npm/bun installs. Use when a package must ship despite the cooldown.
/diff-review
Diff review
Generate a visual HTML diff review, before/after architecture comparison with code review analysis
/fact-check
Fact check
Verify the factual accuracy of a document against the actual codebase, correct inaccuracies in place
/generate-slides
Generate slides
Generate a stunning magazine-quality slide deck as a self-contained HTML page
/generate-visual-plan
Generate visual plan
Generate a visual HTML implementation plan, detailed feature specification with state machines, code snippets, and edge cases
/generate-web-diagram
Generate web diagram
Generate a beautiful standalone HTML diagram and open it in the browser
/plan-review
Plan review
Generate a visual HTML plan review, current codebase state vs. proposed implementation plan
/project-recap
Project recap
Generate a visual HTML project recap, rebuild mental model of a project's current state, recent decisions, and cognitive debt hotspots
/share-page
Share page
Deploy a generated visual-explainer HTML page and return a live Vercel URL
/methodology
methodology
View your cognitive methodology profile and reasoning patterns
/preflight
preflight
Diagnostique l'environnement Cortex et guide la réparation (DB, extensions, modèles)
/why
why
Resolve the ⟦rcpt:id⟧ injection markers in context into presence-in-context evidence (blame path)
/commit
Commit
Please summarize your current changes, generate a commit message in English, then add and commit.
/tag
Tag
Create an annotated git tag with an auto-generated summary of changes since the last tag.
/delegate-review
Delegate review
Run OCR in delegation mode — OCR handles file selection and rules, the host agent performs the actual review.
/review
Review
Run OpenCodeReview (OCR) to review code changes and autonomously apply fixes.
Offline-first Python AI agent that runs a tiny research business: quotes each job against its own costs, collects via Stripe, fulfils with NVIDIA Nemotron, pays…
0 views 0 likesDSH 插件 · 注入式优化器 0.8(主线):你照常说话,它在你发送后,AI接收前把"这一轮到底要什么"理清楚,再把这份理解交给工作 AI(上下文注入) —— 原话不改写,条条带逐字依据。含控制界面(档位/权限/模型/上下文/只读工具)、拦截浮层(思维层+产出层)与真实 token 用量。可明显提升大多数模型的发挥稳…
0 views 0 likesReliable AI Skill + MCP toolkit for agent-driven desktop CAD automation.
0 views 0 likesCurated real-world use cases for Hermes Agent — the self-improving AI agent from Nous Research. Backed by primary sources.
0 views 0 likesAI Agent 教学仓库 | 系统化 LangChain、RAG、LangGraph、MCP 全栈实战代码 | 万字博客详解 | 开源可运行示例 | 从零构建智能体
0 views 0 likes从 0 复刻 WorkBuddy-style 桌面 AI 助手 Harness:24 章 Python 教程,覆盖 Agent Loop、工具调用、记忆系统、Sidecar、沙盒审计、DeepSeek/OpenAI 评测轨迹
1 views 0 likesMCP server and CLI tools for web search and crawling, built on SearXNG and Crawl4AI
2 views 0 likesDelta MCP is a free app that sits between your AI apps and their MCP servers: one program per task instead of one tool call per step, up to 24.1× fewer tokens i…
2 views 0 likesAva turns any Android 5+ device into a voice-first Home Assistant kiosk. Native C++ under the hood, so a 10-year-old tablet still listens, talks, and runs the h…
0 views 0 likesRoblox Studio macOS Window Capture Fix 2026: Real Screenshot Tool Instead of Magenta Playtest Glitch
2 views 0 likesLabTether
2 views 0 likes