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/varalix-digitech-solutions/clone-team/clone-statusgit clone --depth 1 https://github.com/Varalix-Digitech-Solutions/clone-teamWrote 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/varalix-digitech-solutions/clone-team/clone-status)<a href="https://agentmods.dev/commands/varalix-digitech-solutions/clone-team/clone-status"><img src="https://agentmods.dev/badge/commands/varalix-digitech-solutions/clone-team/clone-status.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.00035 | $0.00343 |
| Opus 5 | $0.00017 | $0.00171 |
| Sonnet 5 | $0.00007 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
clone-status 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 5d 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
Report the current state of the clone-team run.
- Resolve the project dir: use
$ARGUMENTSif given, else the current working directory. The state file is<projectDir>/.clone-team/state.json. - Run:
node <clone-team-skill>/scripts/state.mjs status --dir <projectDir>(the skill lives where this command's skill is installed, typically~/.claude/skills/clone-team). - If no state file exists, say so and offer to start a clone with the
clone-teamskill. - Check for an active usage cutoff. If
<projectDir>/.clone-team/HARD_STOPorWRAP_UPexists, the run hit the soft/hard stop and is draining/drained — read the file'sresetsAtand tell the user when the 5-hour window resets (and that/clone-resumeafter that, or the auto-wake timer, picks up from the handoffs). - Summarize for the user in a few lines: what phase we're in, how many sections are done vs. remaining, any flagged sections needing attention, whether the backend doc is complete, and the single recommended next action (resume, address a flagged section, or finish).
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.
- 5d ago First seen · 27 lines · 35 tokens per session scan A 75e025c793b2
clone-status is a command published in the GitHub repository Varalix-Digitech-Solutions/clone-team (20 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 343 once invoked, about $0.0002 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 commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
clarify
Walk through inbox items applying the GTD decision tree. Usage: /gtd:clarify [--id gtd-xxx].