mb-harness

Run deterministic agent executions with guardrails and per-task worktrees.

53|11|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/mrvladd-d/memobank --skill mb-harness
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mb-harness
Source: https://github.com/mrvladd-d/memobank/tree/main/skills/mb-harness
Command: npx skills add https://github.com/mrvladd-d/memobank --skill mb-harness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The mb-harness provides a deterministic, guardrailed environment to run autonomous agent tasks, ensuring repeatable results and auditable gates.

Core Features & Use Cases

  • Defines entry points (AGENTS.md) and concrete quality gates
  • Enables deterministic command execution with per-task worktrees
  • Supports CI integration and memory-bank lint gating for safe operations

Quick Start

Boot the harness to bootstrap deterministic agent execution with guardrails and repeatable worktrees.

Frequently Asked Questions about mb-harness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run autonomous agents deterministically with guardrails for repeatable results?▼

To run agents deterministically, you need a harness that enforces guardrails, per-task worktrees, and quality gates. This ensures repeatable results and reproducible run workflows across your repositories for safe autonomous execution.

What is a deterministic agent harness and when do I need one for my repository?▼

A deterministic agent harness is a controlled environment that manages autonomous agent tasks with strict entry points and quality gates. You need one when your repository requires repeatable agent executions and auditable operational safety.

How do I integrate CI gates with memory-bank linting for safe agent operations?▼

You integrate CI by applying memory-bank lint gating within your agent harness. This setup validates frontmatter-driven documentation and ensures synchronization readiness before any autonomous task completes its workflow.

Can I use per-task worktrees to isolate autonomous agent executions in CI?▼

Yes, you can use per-task worktrees to isolate autonomous agent executions. The harness enables deterministic command execution within these worktrees, ensuring that CI integration and memory-bank operations remain safe and reproducible.

What is the best way to ensure reproducible run workflows for autonomous agent tasks?▼

The best way to ensure reproducible run workflows is to apply a guardrailed harness that defines concrete quality gates, enforces frontmatter-driven documentation, and maintains memory-bank synchronization readiness for every run.

Do I need AGENTS.md entry points to bootstrap deterministic agent execution?▼

Yes, you need AGENTS.md entry points to bootstrap deterministic agent execution. The harness defines these concrete entry points and quality gates to safely guide autonomous tasks from initialization through completion.