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.
git clone --depth 1 https://github.com/s977043/PlanGateWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/s977043/plangate/ai-loop-workflow)<a href="https://agentmods.dev/commands/s977043/plangate/ai-loop-workflow"><img src="https://agentmods.dev/badge/commands/s977043/plangate/ai-loop-workflow/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/s977043/plangate/ai-loop-workflow"><img src="https://agentmods.dev/badge/commands/s977043/plangate/ai-loop-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00000 | $0.02043 |
| Opus 5.5 | $0.00000 | $0.00817 |
| Sonnet 5.5 | $0.00000 | $0.00409 |
| Haiku 4.5 | $0.00000 | $0.00204 |
Grade A, and why
ai-loop-workflow 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 1mo 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ai-loop-workflow
ai-loop-workflow（human-on-the-loop 裁定ループ）を明示起動する。
/ai-dev-workflow（PlanGate 本番フロー WF-00〜07）と対をなす入口であり、
本番フローの置き換えではない。恒久定義（責務・terminal state・C-3'/Human C-3 経路）の
正本は 00_concept.md、適用制限（Phase 1 rollout eligibility）の正本は
rollout-policy.md（eligible run 限定。PlanGate 本番フローの C-3 は常に Human・不変）。
実行手順の正本: skill ai-loop-cycle（1 サイクル = LoopSpec → W チェック →
arbiter 裁定 → exec → rubric grader）。本コマンドは前提確認と起動のみを担う。
パス表記の規約（重要）: 本コマンド中の ai-loop 資材への参照は、環境ごとに 解決先が異なる。上流リポジトリ基準の
docs/**/scripts/**を導入先で そのまま探しに行かないこと（3 経路とも配布対象外であり必ず空振りする）。 参照は<skill_dir>= skillai-loop-cycleが置かれているディレクトリを 解決してから使う（表記・解決規則は skillai-loop-cycleの SKILL.md 冒頭 「パス表記の規約」と同一）:
環境 <skill_dir>plugin 導入先（Claude marketplace） <plugin_root>/skills/ai-loop-cycle/install.sh --claude導入先.claude/skills/ai-loop-cycle/Codex 導入先 .codex/skills/ai-loop-cycle/上流リポジトリ（正本側） .agents/skills/ai-loop-cycle/参照解決順: (1)
<skill_dir>配下の同梱物（references//scripts//schemas/）を第一に読む → (2) 導入先リポジトリが独自の正本（上流のdocs/workflows/ai-loop/に相当するもの）を保持していればそちらを優先する → (3) いずれでも解決できなければ 「正本<path>を参照できなかった」と明示し、 本コマンド内の記述を代替正本として扱い、推測で内容を補わない。 なお上流リポジトリ（正本側）では<skill_dir>配下に同梱物を持たない （references//scripts//schemas/が揃うのは配布物のみ）ため、 上流では (1) が空振りし常に (2) で解決する。 plugin root 直下にdocs/を探しに行かないこと: plugin が配布するのはagents/commands/skills/rules等の定義 ディレクトリのみでdocs/を配布対象として認識しないため必ず空振りする。
引数
$ARGUMENTS に以下の形式で渡される:
run TASK-XXXX— Plan-first の正式入口（TASK ID 必須）。既存の Plan Package （pbi-input / plan / todo / test-cases + C-1/C-2 evidence）を起点に production run を 開始する。LoopSpec は<skill_dir>/scripts/plan_package.pyのderive_loopspec()で Plan Package から決定論派生し、production: true+plan_packageブロックを arbiter へ渡す（契約正本:<skill_dir>/references/c3-prime-contract.md。 上流リポジトリでは順にscripts/ai-loop/plan_package.py/docs/workflows/ai-loop/c3-prime-contract.md）。 TASK ID を伴わない自由文だけのrun <説明>は production run を開始できない （TASK-0872 / #872。Plan Package 束縛の無い run を Wチェックへ進めない）status— 直近 run の状態・decision record・摩擦台帳の要約を表示- （引数なし） — 前提チェックのみ実施して結果を報告
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.
- 1mo ago First seen · 98 lines · 0 tokens per session scan A 0ddc41a751e1
ai-loop-workflow is a command published in the GitHub repository s977043/PlanGate (2 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,043 tokens. 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-09-03.
Other commands, from other repositories
compatibility-audit
Audit all agents for Trinity compatibility by requesting self-diagnostics from each agent.
dispatch-worker
Retired Pattern Z Worker loop; use cli-hierarchy (RFC-0051) instead. See docs/operations/cli-hierarchy.md. AISDLC-763.
wardley
Create strategic Wardley Maps for architecture decisions and build vs buy analysis.
risk
Create comprehensive risk register following HM Treasury Orange Book principles.
at-dsgvo
You are helping an enterprise architect generate an Austrian Data Protection Assessment — the Austrian-specific GDPR layer applied by the Datenschutzbehörde (DSB) under the Datenschutzgesetz (DSG 2018, BGBl. I Nr. 165/1999 as amended). Run this after /arckit:eu-rgpd to add Austrian obligations that go beyond the EU…
gov-reuse
Discover reusable UK government code before building from scratch.