LLM Mart Basic

Independently review the exact result and run its real checks in one context, using isolated resources and without changing the deliverable.

Report the compatibility redirect to `C0`; this retired role cannot perform new work.

Report the compatibility redirect to `C0`; this retired role cannot perform new work.

Report the compatibility redirect to `ap-independent-checker`; this retired role cannot perform new work.

Report the compatibility redirect to `ap-work-group-manager`; this retired role cannot perform new work.

Report the compatibility redirect to `ap-roadmap-author`; this retired role cannot perform new work.

Report the compatibility redirect to `C0`; this retired role cannot perform new work.

Report the compatibility redirect to `C0`; this retired role cannot perform new work.

Report the compatibility redirect to `ap-worker`; this retired role cannot perform new work.

Report the compatibility redirect to `ap-independent-checker`; this retired role cannot perform new work.

Write one dependency-ordered roadmap with owners, integration points, success items, and real checks.

Answer one named planning question with observations tied to the inspected sources; do not write or coordinate the roadmap.

Inspect only enough read-only project information to recommend a route and list the facts behind that recommendation.

Start only ready, non-overlapping roadmap work and combine returned status at the written integration points.

Report the compatibility redirect to `ap-run-coordinator`; this retired role cannot perform new work.

Report the compatibility redirect to `ap-roadmap-author`; this retired role cannot perform new work.

Report the compatibility redirect to `C0`; this retired role cannot perform new work.

Run the Upkeep repo audit locally against any repository path. Use when asked to audit a repo, check docs/spec/asset drift, or run upkeep without GitHub Actions.

Apply Chain-of-Verification (CoVe) prompting to improve response accuracy through self-verification. Use when complex questions require fact-checking, technical accuracy, or multi-step reasoning.

TRIGGER when: adding or upgrading any dependency — library, SDK, framework, API, IaC API version (K8s/Terraform/Helm), CRD, or container image. Use BEFORE writing the call. Forces context7/capy lookup instead of guessing.

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.

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.

Search Hudu knowledge base articles by keyword or phrase

List and filter Huntress agents across organizations

Generate a Huntress billing summary for a period

Triage open Huntress incidents by severity

Deep dive investigation into a specific Huntress incident with remediations

Organization health check covering agents, incidents, and escalations

Review and resolve a Huntress escalation

Generate an ImmyBot software-compliance scorecard for a tenant or the whole fleet

Stage and reconcile an ImmyBot desired-state software deployment to a tenant or computer

List and filter ImmyBot-managed computers, optionally scoped to a tenant

Show ImmyBot maintenance session status — active sessions, or detail and logs for a specific session

Find and execute an ImmyBot PowerShell script on a target computer (destructive, SYSTEM context)

Search the ImmyBot software catalog (per-tenant + global)

Portfolio-wide Inforcer baseline drift report — every managed tenant's alignment vs its assigned baseline, classified aligned / semi-aligned / drifted and sorted drifted-first, with secure score

Single-tenant Microsoft 365 posture snapshot from Inforcer — secure score plus alignment score, band, and the per-policy drift detail against the tenant's assigned baseline

Get an Ironscales AI verdict on a raw email, then act on it with a remediation action

Triage open Ironscales phishing incidents — list by status and severity, investigate, and remediate

Get a Kaseya Quote Manager quote with its sections and line items

Get a Kaseya Quote Manager sales order with its lines and payments

List Kaseya Quote Manager quotes, optionally scoped to a recent window

PiG (Pi in Go) is a faithful Go port of upstream Pi, the TypeScript codebase behind the Pi coding agent. It is a parity-bound translation, not a rewrite: upstre…

An AI Agent that lives in your pocket. Local-first and privacy focused.

Unofficial skill that teaches coding agents to build with TypeSafe AI's Jev: typed decisions, calibrated confidence, and prior art from 150+ community projects.

Adaptive Test-time Learning and Autonomous Specialization

Prediction-market trading engine — Wang Transform pricing on 291K+ contracts; paper-traded across Kalshi · Polymarket · Solana DFlow (Jito bundles) · 633 tests

Knowledge Management for Humans and Agents

Open-source Claude Cowork / Codex / WorkBuddy alternative — a local-first AI office agent that turns one request into real PPTX, DOCX, XLSX and HTML files. Runs…

DeepAgent Code: AI coding agent with persistent memory and control plane