Operational Primitives Directory
A concrete set of agent operating contracts, production policies, command gates, validators, loop patterns, and skills that can be copied into a real repository and used to bound autonomous work before it touches production surfaces.
A production agent contract that forces every run to define intent, allowed scope, blocked scope, validators, rollback, escalation, and completion evidence before changing files.
A production remediation skill for failing tests, contracts, builds, or incident symptoms, with strict intake fields, blocked repairs, two-attempt limits, and JSON evidence output.
A migration skill for deprecated APIs, config formats, package imports, and schema contracts, requiring inventory counts, batch limits, protected path checks, and final validator evidence.
A security review skill for changed code, dependencies, auth, input handling, infrastructure, and deployment paths, with critical finding stop rules and scanner evidence requirements.
A troubleshooting skill that gathers structured runtime, git, package, artifact, environment-name, and optional health-check diagnostics before choosing remediation.
A pre-execution hook that checks planned files, operations, validators, cost, and rule-specific requirements before allowing autonomous work to proceed.
A command hook that normalizes shell requests, denies destructive git and shell fragments, and escalates commands outside an explicit allow list.
A post-run hook that emits outcome, duration, changed files, validators, policy decisions, attempts, remaining risk, escalation state, and cost metrics.
A production policy with default escalation, explicit blocked paths and operations, billing and migration validator requirements, and evidence rules.
A git policy that blocks protected branch writes, destructive history commands, unrelated dirty worktree changes, and unvalidated merge attempts.
A billing validator that protects totals, idempotency, refunds, integer currency handling, provider side effects, and secret-free logs with required contract commands.
A coverage validator that fails changed production files without test evidence and escalates when coverage cannot run or thresholds must be lowered.
A bounded remediation loop with named phases, required evidence per phase, adaptation rules, two-attempt maximum, and explicit escalation entry conditions.
A fill-in envelope that gives contributors a concrete starting structure to submit new operational primitives.
The JSON schema contract that every operational primitive must satisfy: kind, intent, scope, evidence, and escalation.
No operational primitives match your search query.