15 tagged llm tooling, measured the same way as everything else here.
Browse within: starter-template 6
Junhanliu-dev/espalier-engineering
Agent
Implementation agent for {projectname} — writes code that follows the project's Espalier rules, layer specs, and Solution Selection Ladder (conventions first, correctness within them, clarity then brevity break ties). Spawned by the pipeline at Stage 3 (implementation — under folded test-mode this includes writing the…
Junhanliu-dev/espalier-engineering
Agent
Review agent for {projectname} — checks a diff against the project's Espalier conventions, layer boundaries, runtime surfaces, production-readiness seeds, test meaningfulness, and (advisory) minimalism + readability. Spawned fresh by the pipeline each Stage 4 review round (code AND its tests, one verdict) and for the…
Junhanliu-dev/espalier-engineering
Agent
Security audit agent that checks the trust boundary — never trust data from the frontend — on a pipeline change (Stage 4 panel) or repo-wide (/espalier-audit repo-audit mode). Audits client input on the money / identity / permission / ownership / state axes reaching an authorization or persistence sink; self-noops on…
Agent
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
Agent
Compare two outputs WITHOUT knowing which skill produced them.
Agent
Evaluate expectations against an execution transcript and outputs.
Agent
Use this agent when a zforge phase has reported DONE and its evidence must be independently verified before the planner accepts it. Typical triggers include /zforge:feature-orchestrate accepting a REPORTED phase during a long chain, and any run where the planner's context is the constrained resource. It reconciles the…
Agent
Use this agent when a phase of a zforge feature plan is ready to implement and its work should run in its own context. Typical triggers include /zforge:feature-orchestrate spawning a READY phase, resuming a phase whose agent was interrupted mid-run, and re-running a phase after a decision was rejected in review. See…
Agent Claude Code
Run lint, build, and tests on demand and report pass/fail with the relevant errors. Use when validating that a change compiles and the suite is green.
Agent Claude Code
Review a diff and return a summary plus issues, making no edits. Use for reviewing a branch, PR, or working-tree change.
Agent Claude Code
Maintain documentation - keeps decisions.md, errors.md, and CLAUDE.md files accurate. Use when docs have drifted from the code.
Agent
Writes and modifies code files based on the plan.