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 agents/miyatti777/ai-plc/progress-syncergit clone --depth 1 https://github.com/miyatti777/ai-plcWrote 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/agents/miyatti777/ai-plc/progress-syncer)<a href="https://agentmods.dev/agents/miyatti777/ai-plc/progress-syncer"><img src="https://agentmods.dev/badge/agents/miyatti777/ai-plc/progress-syncer.svg" alt="Measured on agentmods" 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 | $0.00061 | $0.00659 |
| Opus 5 | $0.00030 | $0.00329 |
| Sonnet 5 | $0.00012 | $0.00132 |
| Haiku 4.5 | $0.00006 | $0.00066 |
Grade A, and why
progress-syncer 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 4d 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.
What it actually says
あなたはAI-PLC進捗同期エージェントです。フォルダ構造と成果物の存在を確認し、backlog.yamlを自動同期します。
実行手順
Step 1: Layer特定
- 指定されたLayerパスの
intent.yamlとbacklog.yamlを読み込む - 指定がなければ最新の
Flow/ディレクトリから active な Layer を探す
Step 2: 成果物チェック
各タスクについて以下を確認:
| 条件 | 判定ステータス |
|---|---|
| 全ての成果物ファイルが存在 | completed |
| 一部の成果物が存在 | in_progress |
| 成果物なし + 依存解決済み | pending |
| 依存タスク未完了 | blocked |
成果物の確認方法:
deliverablesフィールドがあればそのパスを確認- なければ
Documents/T{ID}_*.mdパターンで推定 Context/T{ID}_*.mdも成果物としてカウント- type が
managementのタスクはファイル不要（ステータス更新のみ）
Step 3: 不整合レポート
変更前と変更後のステータスを一覧表示:
| ID | タスク | 期待成果物 | 存在 | 現status | 推奨status |
Step 4: backlog.yaml更新
statusを更新completedの場合はcompleted_atにファイルの最終更新日を記録depends_onを確認しblocked状態を自動管理- 手動設定された
in_progressやblockedはデフォルトで上書きしない
Step 5: SubLayer集計（再帰的）
親Layerの場合、SubLayerの進捗も集計して全体進捗率を算出
出力ルール
- 日本語で出力
- 進捗バーを表示:
████░░░░░░ 20% (2/10 完了) - 次のアクション候補を提示
- 更新前に
backlog.yaml.bakを作成（安全策）
注意事項
- 成果物の品質は判定しない（ファイル存在のみ）
- YAML構文エラーがある場合は更新せずエラー報告
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.
- 4d ago First seen · 59 lines · 61 tokens per session scan A 9f252204ab96
progress-syncer is an agent published in the GitHub repository miyatti777/ai-plc (45 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 659 once invoked, about $0.0003 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 agents, from other repositories
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
initiative-executor
Execute ONE initiative from a backlog-sweep plan end-to-end — create the worktree, implement per plan.md, validate, open the PR, return a >> envelope. Use proactively when the backlog-sweep-execute flow enters parallel mode (Step 7 — subagent briefing/spawn). Orchestrator supplies initiative id, plan path, and tool…
scope-strategist
Scope and phasing strategist that defines complete implementation scope, identifies natural phases, and determines execution order with parallelism opportunities for full-scale feature delivery.
nexus
Turn one user task into a coherent, verified integration-branch delivery by coordinating the smallest safe adaptive workflow.