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/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-resume)<a href="https://agentmods.dev/commands/varalix-digitech-solutions/clone-team/clone-resume"><img src="https://agentmods.dev/badge/commands/varalix-digitech-solutions/clone-team/clone-resume.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.1 | $0.00045 | $0.00598 |
| Opus 5 | $0.00023 | $0.00299 |
| Sonnet 5 | $0.00009 | $0.00120 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
clone-resume 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 7d 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
Resume the clone-team run. Follow references/state-and-resume.md and
references/orchestration.md.
- Resolve the project dir (
$ARGUMENTSor cwd) and read<projectDir>/.clone-team/state.json. Re-establish full context: goal, target, stack, creds file path, paths, run-config. - Reconcile with disk. Run
node <skill>/scripts/state.mjs reconcile --dir <projectDir>— it keepsdonesections whosetargetFileexists, marks on-disk-but-unverified filesbuiltfor test-first re-validation, demotesdone-without-file topending, and clears any staleWRAP_UP/HARD_STOPusage sentinels the drained run left behind (so the relaunched loop isn't immediately re-tripped). When unsure whether a half-finished section is trustworthy, prefer re-verification — re-testing is cheap insurance. 2.5. Restart the usage watchdog — a resume is a fresh Workflow, so it needs its own watchdog:node "<skill>/scripts/usage-watchdog.mjs" start --dir <projectDir>as a backgroundBash. Sections deferred by a prior usage-cutoff resume from theirdocs/research/components/<slug>.handoff.mdfiles automatically. - Relaunch the loop:
- Same session with a still-valid
lastRunId→ call theWorkflowtool with{ scriptPath: "<skill>/workflows/clone-build-loop.js", resumeFromRunId: "<lastRunId>" }. Cached agent calls return instantly. - Otherwise (new session / cutoff) → compute remaining work with
node <skill>/scripts/state.mjs remaining --dir <projectDir>and launch the Workflow fresh withargs.sectionsset to only those not-done sections (the durable, journal-independent path). Re-pass goal, stack, creds path, personas (readagents/*.md), and run-config inargs.
- Same session with a still-valid
- Record the new
runId(state.mjs set-run), set the phase, and let it run. If the backend doc is incomplete, ensure that track resumes too. - Tell the user what's resuming and roughly what's left.
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.
- 7d ago First seen · 42 lines · 45 tokens per session scan A 8310ef46d656
clone-resume is a command published in the GitHub repository Varalix-Digitech-Solutions/clone-team (20 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 598 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
frontend-e2e
Perform a thorough live E2E test of a frontend web application using browser-bridge MCP tools. Tests every page, interactive element, form, navigation flow, responsive breakpoint, and accessibility rule through real browser interaction.
health-check
Perform a comprehensive, read-only end-to-end review of any portfolio app across three layers — Frontend (E2E), Database integrity, and Audit Log & User Activity — and produce a structured, observations-only report. Optionally, on explicit opt-in, generate (never apply) the infrastructure provisions needed so future…
spreadsheet-audit
Perform a 6-step audit of an Excel spreadsheet for formula correctness, formatting consistency, data integrity, boss-auditable simplicity, and spec compliance. Uses the excel-screenshot MCP server tools — no Excel installation required.
stub-check
Perform a thorough 3-phase audit of the current project's codebase to find code that is unfinished, shallow, skeletal, or not production-ready. Phase 0.5 runs a Perplexity research reconnaissance using GitHub connectors (runs in parallel with Phase 1). Phase 1 uses local scanning (Grep/Glob/Read) independently. Phase…
orchestrator-new
YOU ARE A PROJECT ARCHITECT. You take a project idea from the user, research the optimal architecture via Perplexity, generate a comprehensive BLUEPRINT.md with all phases and sub-phases, then route to /orchestrator or /orchestrator-multi for execution. You do NOT implement code yourself — you design and delegate.
council-extract
Extract a completed Perplexity Model Council response from the current browser tab, converting it to structured markdown with model attribution, and save to disk.