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 commands/anshulixyz/multi-agent-loop-kit/tickgit clone --depth 1 https://github.com/anshulixyz/multi-agent-loop-kitWhat 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.00155 |
| Opus 5 | $0.00009 | $0.00077 |
| Sonnet 5 | $0.00004 | $0.00031 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
tick 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.
What it actually says
Run a full loop sweep in one pass:
bash "${CLAUDE_PLUGIN_ROOT}/bin/loop-tick"
It resolves your primary checkout automatically (so the standup's derived files land in the right place), then runs the status board, the Beacon scan, the radar summary, and the standup back to back. Synthesize the four outputs into a single operator briefing: who's working on what, what's stale or blocked, what's on the radar, and what needs the operator's decision right now.
(If the plugin's bin/ is on your PATH, loop-tick is the same command.)
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 · 18 lines · 18 tokens per session scan A 6f48b00871e4
tick is a command published in the GitHub repository anshulixyz/multi-agent-loop-kit (5 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 155 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-31.
Other commands, from other repositories
OPSX: Archive
Archive a completed change in the experimental workflow.
vibe-audit
Run a structured, autopilot codebase audit against curated coding standards and produce an actionable remediation plan with sprint-based prioritization.
pm-outline
Generate detailed project outline and draft charter from user intent (empty/new projects).
show-status
作用: 显示当前 PaperFit 任务的运行状态、缺陷消除进度、视觉优先级、修复计划摘要和下一步行动；这是当前默认的“摘要 / 解释”入口。.
milestone-review
PitWay: Role-based milestone review workflow (start/brief/record/report/decide).
status
Show current project state and task status.