LLM Mart Basic
@llm-mart · Joined Jun 2026
Abnormal Security threat detection: threat types (BEC, phishing, malware, socially-engineered attacks, spam, graymail, credential theft), attack vectors, severity assessment, remediation actions, and investigation workflows.
Atera alerts: alert types, severity levels, alert sources, the acknowledge/resolve lifecycle, and alert-to-ticket conversion.
Atera REST API fundamentals: X-API-KEY header authentication, OData-style pagination, the 700 requests/minute rate limit, endpoint conventions, and error handling.
Atera customers and contacts: customer records and fields, contact management, custom fields, and customer lifecycle operations.
Atera service desk tickets: ticket fields, statuses, priorities, comments, work hours, and billing duration.
Auvik alerts: severity tiers, status lifecycle, dismissal semantics, and the common alertName patterns that show up in MSP NOC queues.
Auvik MCP fundamentals: the JSON:API envelope shape, basic-auth credential model, region routing, cursor-based pagination, rate-limit handling, and the v1 vs v2 device API distinction.
Auvik device records: device types, manageStatus and onlineStatus, lifecycle and warranty fields, and choosing between the v1 list endpoint and the detailed device endpoints.
Auvik network and interface entities: the network entity model, IP-range scoping, interface-to-device relationships, and adminStatus vs operStatus.
Autotask REST API fundamentals: header-based authentication, zone detection, the query/filter DSL (14 operators, logical grouping, includes), pagination, rate limits, and CRUD conventions across the 215+ entity PSA.
Autotask billing item retrieval, approval-level workflows, and invoice search — covering billing item types, approval status filtering, and reconciliation of billable work against invoices for MSP finance teams.
Autotask Configuration Item (CI) asset management: CI types and categories, lifecycle status codes, the CI field schema, related-item relationships, DNS records, notes, and contract/billing associations for MSP infrastructure tracking.
Autotask contract and service agreement management - contract types (recurring services, block hours, time & materials, fixed price, retainer), service/service bundle associations, SLAs, and how contracts drive billing for MSP account managers.
Autotask CRM entities - companies (accounts), contacts, and sites/locations - including field references, company type classifications, and how these records underpin tickets, contracts, and projects for MSP account management.
Autotask expense report and expense item structure - the report/item parent-child relationship, approval status workflow, expense categories, payment types, and the billable vs reimbursable distinction for MSP operational expenses.
Autotask picklist and reference-data lookups — queues, ticket statuses, ticket priorities, and project phases — the instance-specific configured values required before creating or filtering tickets and other entities.
Autotask product catalog structure - Products, Services, and Service Bundles - and how Price Lists override default unit pricing. Covers product/service fields, inventory tracking, and cost-vs-billing margin analysis for MSP quoting and procurement.
Autotask project structure - projects, phases, tasks, and milestones - including project and task fields, status values, resource assignment, and how project work links to contract billing for MSP project managers.
Autotask quote structure and line items - quote item types (product, service, service bundle, labor, expense, shipping), the mutually-exclusive catalog reference rules, and the three discount mechanisms (unit, line, percentage) used to build customer proposals.
Autotask Service Call data model - the ServiceCall / ServiceCallTicket / ServiceCallTicketResource three-layer structure - covering fields, status codes, and how tickets and technicians (resources) are linked to scheduled work.
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.
Use MCP Inspector to connect to local or remote servers, inspect capabilities, call tools, read resources, test prompts, and diagnose failures before release.
Build an MCP server in TypeScript with focused tools, validated schemas, local and remote transports, Inspector tests, and production security controls.
An MCP server exposes tools, resources, or prompts through a standard protocol so an AI application can discover and use external capabilities.
/forge-oauth-callback
Forge oauth callback
Scaffold a complete OAuth2 callback + init Hono route pair (code exchange, PKCE, KV token storage) for a named provider
/forge-press-release
forge-press-release
Scaffold an Amazon-style working-backwards press release for any feature, in Brian's voice. Outputs to docs/decisions/PR-{slug}.md and prints to stdout.
/forge-skill-from-vendored
Forge skill from vendored
Vendor a third-party skill repo/URL into the owned layer — clone, compress to house style, cross-link, commit — in one keystroke
/forge-stack-pack
Forge stack pack
Batch-forge Brian's entire stack as skills + MCP servers in one prompt; skips already-forged entries; applies automatic pruning when tool count >100
/forge-webhook-handler
Forge webhook handler
Scaffold a complete webhook handler (Hono route + sig verification + D1 idempotency + R2 dead-letter) for a named vendor
/forge-webhook-skill
Forge webhook skill
Scaffold a complete webhook receiver for any provider from an AsyncAPI YAML spec or a JSON event-type list
/generate-prp
Generate prp
Generate a Project Requirements Plan (PRP) — research-driven, ULTRATHINK-gated, confidence-scored implementation blueprint
/improve-lint
improve-lint
Run the AI-augmented lint self-improvement loop on the current project. Scans `.lint-history/` for recurring violation patterns (≥3 hits in 30d window), drafts a Claude-ready prompt to author a new semgrep rule for the top candidate, and surfaces the proposal under `.lint-history/proposals/<ts>.md`. Non-blocking analysis. See rules/lint-doctrine.md § Self-improving.
/install-lint-stack
install-lint-stack
Bootstrap industry-leading lint+autofix+commit-hygiene stack on the current project. Drops in lefthook, oxlint, ESLint, Prettier, Stylelint, markdownlint, ruff, shellcheck, shfmt, yamllint, hadolint, actionlint, jscpd, knip, semgrep, gitleaks, commitizen + git-cz-emoji (emoji-mandatory commits), and semantic-release. Idempotent — re-runs upgrade safely. See rules/lint-doctrine.md.
/list-arcs
list-arcs
Surface all retrospective documents with key shape metrics; compare arcs deliberately.
/migrate-all-to-hardened
Migrate all to hardened
Batch-migrate every hardened MCP server in mcp-servers/ from its original source to its hardened counterpart in one sweep
/migrate-skill
Migrate skill
Generic skill-version migration — works for hardened/v2/experimental→stable promotions across MCP servers, skills, hooks, commands. Mirrors /migrate-to-hardened with broader detection.
/migrate-to-hardened
Migrate to hardened
Automate the unhardened → hardened MCP server cutover — build, smoke-test, register, and archive in one shot
/multimedia-enrich
Multimedia enrich
Progressive multimedia enrichment pass — add high-value audio/video/image/interactive to a site, run again and again
/plan-execute-verify-repair
Plan execute verify repair
Run the autonomous-engineering operating loop on a task (plan→implement→verify→repair→report)
/post-arc-retrospective
Post arc retrospective
Capture the cumulative output of a /loop arc into a single auditable retrospective document; scans the heymegabyte-claude-skills plugin for modified files, categorizes by directory, counts LOC delta, extracts tool counts from MCP servers, and writes a timestamped report to retrospectives/
/prepare-multi-file-brief
prepare-multi-file-brief
Turn a comma-separated list of file paths into a fully structured Pattern A agent brief — ordered writes, per-file schemas, and a verification step baked in.
/prepare-skeleton-brief
prepare-skeleton-brief
Turn Pattern B from agent-resilience-discipline into a one-keystroke agent brief for a single-file deliverable < 300 lines.
/process
Process
Chain the full Superpowers process flow — brainstorm → plan → worktree → build → review → finish — on one slash command
/prune-mcp-tools
Prune mcp tools
Reduce a forge-generated MCP server's tool surface. Comment out low-value tools (preserving reversibility), update the README tool count, and emit a pruning report.
Make any song you can imagine
38 views 0 likesLeading AI-powered video generation platform that specializes in creating hyper-realistic talking avatars
37 views 0 likesHermes Agent is an open-source, self-improving autonomous AI agent developed by Nous Research
36 views 0 likesKilo Code is a popular, open-source AI coding agent and "agentic engineering" platform designed to help developers build, refactor, and debug software faster
33 views 0 likesGeneral-purpose agent in one static Go binary. ReAct loop, ACP server for IDEs, OpenAI-compatible REST API with embedded web UI, Telegram gateway, cron schedule…
18 views 0 likesAutonomous agent framework with structured memory, safety hooks, and loop management. Built by the agent that runs on it.
19 views 0 likesTSP自托管、零运维的 A 股「选股 + 监控 + 回测」量化工作台 | 基于 TickFlow 数据源 | LLM能力驱使策略定制+个股分析+复盘 | 自由接入第三方数据源与个性化扩展数据 | 个人开源 ,非TickFlow官方项目
14 views 0 likesCurated, verified Agent Skills powered by ModelStudio.
17 views 0 likesRun Claude Code, Codex, Antigravity, Cursor Agent and OpenCode as one runtime — persistent sessions, multi-agent councils, an OpenAI-compatible endpoint, an MCP…
16 views 0 likespi had nothing (nothing), so I made something (something) — sorry mariozechner-senpai, I went ahead and lovingly soiled your pure pi for you. opinionated fork o…
13 views 0 likesA persistent workspace for development work that self-improves and continues beyond one session.
32 views 0 likesOpen-source memory and context for user-aware agents: scoped memory, provenance, retrieval quality, correction, boundaries, evals, and MCP/HTTP access.
19 views 0 likes📚 A zero-dependency, git-backed micro-lesson library for AI Agents to asynchronously share and search verified debugging experience. Python stdlib only. | http…
28 views 0 likesDeterministic, local-first memory and guardrails for AI coding agents with no LLM in the hot path.
30 views 0 likesDeterministic spec-orchestration for local LLMs in the pi coding agent — drives prompts through refine→research→grill→compose→critique, with bundled web/docs/fe…
19 views 0 likesNative Safari browser automation for AI agents. 97 tools via AppleScript — zero overhead, keeps logins, runs silently in background. Drop-in alternative to Chro…
31 views 0 likesAgent OS: keep specialist agents in a hub, spin up a temporary orchestrator per task. Local-first, works with any model.
14 views 0 likesGit for agent memory. Branches, diffs, PRs, and rollback for what your agents know.
31 views 0 likesMulti-Provider AI Gateway - No personal logs by design. Model autodiscovery, Failover groups, High availability, Android companion app, and more - "Because we h…
15 views 0 likesProduction-grade MCP server for MikroTik RouterOS with secure AI-native network automation.
27 views 0 likes