agent-stdlib

Set up and explain the lock-file autonomy loop for running unsupervised agents on one shared repo.

Run an orchestrator-worker research pass that decomposes a question into parts, dispatches parallel research-worker subagents, and synthesizes a cited answer.

Worker subagent for an orchestrated research run. Takes one objective and a notes-file path, searches broad-to-narrow, writes cited findings to the file, and returns a short summary. Dispatched by the /research command, not for direct use.

Build automated evaluations for an AI agent from scratch: collecting tasks from real failures, choosing code/model/human graders, picking pass@k vs pass^k, building an isolated harness, and keeping the suite honest over time. Use this whenever someone wants to measure, benchmark, or regression-test an agent, write an eval harness for an LLM agent, decide how to grade non-deterministic output, set up an LLM-as-judge, or asks any version of "how do I know if my agent is actually getting better." Trigger even when they say "tests for my agent," "eval set," or "agent benchmark" rather than the word "evals." Not for container or resource limits making scores flaky across runs; that's calibrate-eval-infrastructure.

Stop the machine from deciding your benchmark. Configure and validate the container and runtime resources for an agentic coding eval so infrastructure noise stays inside statistical bounds instead of swinging scores more than the models do. Use this whenever someone runs SWE-bench or any agentic coding benchmark in containers, sees scores jump between runs for no code reason, suspects OOM kills or flaky infra are skewing results, sets container memory or CPU limits for an eval harness, or wants to trust a leaderboard delta. Trigger on "my benchmark scores are inconsistent," "OOM during eval," "how much memory should the eval container get," and similar. Not for designing the eval tasks or graders themselves; that's build-agent-evals.

Design the tool interface for a coding agent so the model stops misusing it. Covers the minimal two-tool scaffold (a bash tool plus a file editor), exact single-match string replacement, absolute-path rules, and error-proofing the tool descriptions so common model mistakes become impossible. Use this whenever someone is building a coding agent or SWE-bench-style harness, designing a bash or file-edit tool for an agent, deciding how much scaffolding to impose, or debugging an agent that keeps editing the wrong place, fumbling multi-line edits, or escaping shell commands wrong. Trigger on "build a coding agent," "str_replace tool," "agent keeps breaking the file," and similar. Not for general MCP or service tool design; this is the bash plus file-editor interface specifically.

Structure a long-lived agent service so any part can crash and resume. Decompose it into brain (model plus harness), hands (ephemeral sandbox and tools), and session (a durable event log), each replaceable on its own, with wake/resume semantics and credentials kept out of the execution environment. Use this whenever someone designs a production or long-running agent backend, asks how to make agents crash-recoverable or resumable, worries about losing session state when a container dies, needs to scale agents as a service, or asks where to keep credentials for an agent that runs code. Trigger on "agent infrastructure," "resume an agent after a crash," "agent runs for hours," "where do tokens live," and similar. Not for parallelizing work across agents or coordinating a shared repo; see multi-agent-orchestration and parallel-autonomous-agents.

Run an orchestrator-worker system for breadth-first research: a lead agent plans, spawns three to five subagents with their own context windows, and synthesizes their findings. Covers when multi-agent actually beats a single agent and when it just burns tokens, how to delegate so subagents do not overlap, broad-to-narrow search, writing findings to a filesystem, and how to evaluate the system. Use this whenever someone wants to parallelize research or exploration across agents, asks how to coordinate a lead and subagents, considers a multi-agent setup, or asks whether multi-agent is worth it for their task. Trigger on "orchestrator and workers," "parallel research agents," "lead agent spawns subagents," "should this be multi-agent," and similar.

1 hook across 1 event