Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/brifl/coding-agent-orchestration/vibe-loopnpx skills add brifl/coding-agent-orchestration --skill vibe-loopgit clone --depth 1 https://github.com/brifl/coding-agent-orchestrationWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00018 | $0.00743 |
| Opus 5 | $0.00009 | $0.00371 |
| Sonnet 5 | $0.00004 | $0.00149 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
vibe-loop scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Drive the Vibe workflow deterministically for a target repository.
This skill uses .vibe/STATE.md and .vibe/PLAN.md to recommend the next loop prompt and to validate invariants.
Inputs
- Repo root path (default: current working directory)
- Optional:
--strictvalidation for CI-grade checks
Runtime helpers
- Source repo:
tools/agentctl.pyis the editable dispatcher source. - Installed skill:
scripts/agentctl.pyis generated fromtools/agentctl.pyby bootstrap tooling. - Skill-owned wrapper:
scripts/vibe_next_and_print.py.
How to use
- Show current status:
- Source repo:
python3 tools/agentctl.py --repo-root . --format json status - Installed skill directory:
python3 scripts/agentctl.py --repo-root . --format json status
- Source repo:
- Recommend next loop:
- Source repo:
python3 tools/agentctl.py --repo-root . --format json next - Installed skill directory:
python3 scripts/agentctl.py --repo-root . --format json next
- Source repo:
- Recommend next loop using a named workflow (for example
workflows/continuous-refactor.yaml):- Source repo:
python3 tools/agentctl.py --repo-root . --format json next --workflow continuous-refactor - Installed skill directory:
python3 scripts/agentctl.py --repo-root . --format json next --workflow continuous-refactor - Pass the workflow file stem (
continuous-refactor), not the.yamlfilename.
- Source repo:
- Validate invariants:
- Source repo:
python3 tools/agentctl.py --repo-root . --format json validate - Installed skill directory:
python3 scripts/agentctl.py --repo-root . --format json validate - Strict mode (recommended in CI): add
--strict
- Source repo:
- Record loop completion from emitted LOOP_RESULT:
- Source repo:
python3 tools/agentctl.py --repo-root . --format json loop-result --line 'LOOP_RESULT: {...}' - Installed skill directory:
python3 scripts/agentctl.py --repo-root . --format json loop-result --line 'LOOP_RESULT: {...}'
- Source repo:
- Print the next loop prompt body directly:
- Run:
python3 scripts/vibe_next_and_print.py --repo-root . --show-decision - The helper uses the managed bundle containing the wrapper.
CODEX_HOME/AGENT_HOMEis only a fallback for incomplete legacy copies.
- Run:
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 57 lines · 18 tokens per session scan A 49530e77701d
vibe-loop is a skill published in the GitHub repository brifl/coding-agent-orchestration (20 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 743 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
mcporter
List, auth, and call MCP servers/tools from the terminal.
📝 任务完成后归档
重要提醒: 每次完成复杂调试或开发任务后，主动执行此流程！ 将学到的经验归档为 skill，供以后参考。不要等用户提醒。.
oracle
Best practices for using the oracle CLI (prompt + file bundling, engines, sessions, and file attachment patterns).
agent-mode
Unified tool for managing agent LLM modes (add, remove, update, list, switch).
agento11y-prod-setup
Sets up production evaluation and guardrails for a DEPLOYED AI agent in Grafana Agent Observability, grounded in the agent's own code and its real ingested traffic. The judgment layer on top of the agento11y skill: it reads the agent's source (system prompt, tools, entrypoint) AND samples its live traffic via gcx…
mcp-scripting
Write mcpScript JavaScript for discovering, inspecting, and calling MCP tools.