@agent-pattern-labs/agent-workbench

@agent-pattern-labs/agent-workbench

Local operator workbench for ISO-based agent harness projects.

agent-workbench discovers harness projects on disk and summarizes the configuration, scripts, MCP servers, and local state files an operator usually needs before deciding what to run next.

Install

npm install -D @agent-pattern-labs/agent-workbench

Or run it ad hoc:

npx @agent-pattern-labs/agent-workbench scan ~/AgentPatternLabs

CLI

agent-workbench scan [root] [--max-depth 3] [--json]
agent-workbench status [project] [--json]
agent-workbench doctor [root] [--max-depth 3] [--json]

scan is the default command:

agent-workbench ~/AgentPatternLabs

The scanner recognizes:

• ISO projects with agent.md, iso/, models.yaml, or generated harness files.
• JobForge projects and packages.
• @agent-pattern-labs/leads-rig projects and packages.
• @agent-pattern-labs/profile-scribe-rig projects and packages.
• Generic package workspaces that depend on ISO or Agent Pattern Labs packages.

Library API

import {
  discoverProjects,
  readProjectStatus,
  summarizeWorkspace,
  formatSummary,
} from '@agent-pattern-labs/agent-workbench';

const summary = summarizeWorkspace('/Users/charlie/AgentPatternLabs');
console.log(formatSummary(summary));

What It Checks

For each discovered project, the workbench reports:

• project kind and package name
• common operational scripts such as verify, smoke:iso, build:config, trace:list, and guard:audit
• agent/harness markers such as AGENTS.md, agent.md, iso/, models.yaml, .codex/config.toml, .mcp.json, and opencode.json
• MCP server names found in JSON MCP config or Codex TOML config
• local event ledgers, cache directories, and trace-like directories

The package is intentionally local-only. It does not upload traces, read secrets, or call model APIs.