Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.
The English summary is being prepared. Showing the original description.
hybridlabor-api/aos6Updated Oct 16, 2026
FreePublished on GitHub
loop-templates
Use when a task should repeat on a schedule or until a condition holds (CI until green, follow a PR to merge, review rounds until no blockers, daily session summary). Ships ready prompt templates with run and duration limits, stop conditions and go-gate safety rules, and per-harness loop invocation.
The English summary is being prepared. Showing the original description.
See how to installFiles included (5)
- SKILL.md1.9 KB
- references/ci-until-green.md1.6 KB
- references/daily-summary.md1.4 KB
- references/pr-to-merge.md1.7 KB
- references/review-rounds.md1.7 KB
SKILL.md (original)
Review the instructions the agent will receive before you install.
Loop templates
Reference prompts for /bdb-aos:loop. Pick a template, fill the placeholders, hand it to the harness loop mechanism.
| Template | File | Max runs / duration |
|---|---|---|
| CI until green | references/ci-until-green.md | 10 / 2 h |
| Follow a PR to merge | references/pr-to-merge.md | 20 / 4 h |
| Review rounds until no blockers | references/review-rounds.md | 5 / 3 h |
| Daily session summary | references/daily-summary.md | 7 days |
Per-harness invocation
- Claude Code: built-in
/loop <interval> <prompt>; omit the interval to let the model self-pace. - OpenCode:
opencode-loop, an opt-in package (AOS_OPENCODE_OPTIONAL=loop, seedocs/opencode-setup.md). Do not schedule gated commands through its shell loop. - Codex:
/goalwith the filled template as the goal. Codex has no/loop. Codex /goal is unverified in AOS docs; confirm withcodex --help. - agy: unverified, no loop mechanism confirmed. Manual repeat: re-send the filled template yourself at each interval and stop at the limits.
Rules for every loop
- A loop prompt never issues a GO, never types or runs
gogate, never sets a mode or grant. - Act on a guarded step (merge, push, publish) only if the human's immediately preceding message is a literal GO or a valid grant (scope and time fit) covers the action. A loop iteration never satisfies the first condition, so it must STOP and report instead of continuing a blocked guarded step.
- Every template carries explicit limits and a stop condition; never remove them.
Reviews
No reviews yet. Tell others what you thought.
Comments
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
More skills from this repository
agent-memory-mcp
FreeUse when a hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).
The English summary is being prepared. Showing the original description.
hybridlabor-api/aos6Updated Oct 16, 2026
agent-pipeline
FreeReference for how BDB structures autonomous software engineering work — the seven-node dispatcher graph (Architect, TechLead, UI/UX, Engineering, Media/EventTech, Reviewer, Shipping) that /startcycle-graph actually runs. Use when you need the high-level lifecycle framing without inventing your own process.
The English summary is being prepared. Showing the original description.
hybridlabor-api/aos6Updated Oct 16, 2026
Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.
The English summary is being prepared. Showing the original description.
hybridlabor-api/aos6Updated Oct 16, 2026
Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.
The English summary is being prepared. Showing the original description.
hybridlabor-api/aos6Updated Oct 16, 2026
agenttrail
Freeagenttrail: live map of a multi-agent build in the browser: which plan component is being worked on, by which agent or harness, what is done and what is stuck. Use when a multi-agent pipeline starts (/startcycle, /startcycle-graph, /teamwork-preview) or after a plan-canvas approve, when the user asks to see what the agents are doing ("live map", "build board", "who is running now"), or by yourself whenever a multi-agent run is under way — no user prompt needed.
The English summary is being prepared. Showing the original description.
hybridlabor-api/aos6Updated Oct 16, 2026