Data
01Agent
Answer telemetry questions with data queries using Kusto Query Language (KQL).
11 tagged parallel agents, measured the same way as everything else here.
Browse within: code-archaeology 6opus 6superpowers 6
Agent
Answer telemetry questions with data queries using Kusto Query Language (KQL).
Agent
Agent for demonstrating VS Code features.
Agent
Specialist in developing the Agent Sessions Window.
Agent
Use when a Compound V manifest (or a plan with a verified Partition Map) is ready to execute and you want to offload the batched, manifest-driven, multi-backend parallel dispatch. Refuses to start if partition-reviewer did not return PASS or if no audit context exists. Runs the git-derived scope gate after every job…
Agent
Use when a Compound V manifest (or a plan with a Partition Map) is ready and you need to verify its partition is genuinely disjoint and its invariants hold BEFORE executing parallel dispatch. Runs compound-v-validate-manifest.py as the deterministic backing gate, then returns PASS or FAIL with specific violations…
Agent
Use to run Compound V's three-pass Review Gate. Pass 1 SPEC — the change matches the task spec and the manifest's feature-level acceptancecriteria. Pass 2 QUALITY — code quality, no regressions, no fabricated metrics. Pass 3 INTEGRATION — cross-job seams hold and the build is green. DONE is gated on all three passing.…
Agent
The Bad — the judgment executor of the good-bad-ugly workflow. Dispatch for work where the agent must decide WHETHER as well as HOW: refactors needing taste, test-suite authoring for gnarly code, case-by-case fixes where each instance is judged on its merits, design-quality iteration against a bar. Give it a fenced…
Agent
The Ugly — the mechanical executor of the good-bad-ugly workflow. Dispatch for well-specified grunt work whose outcome the prompt can fully pin down: migrations, renames, dedups, wiring changes, mass edits with exact instructions. Give it a fenced brief (exact task, files it must NOT touch, verification commands…