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-updategit 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-update)<a href="https://agentmods.dev/commands/varalix-digitech-solutions/clone-team/clone-update"><img src="https://agentmods.dev/badge/commands/varalix-digitech-solutions/clone-team/clone-update.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.00053 | $0.00883 |
| Opus 5 | $0.00026 | $0.00441 |
| Sonnet 5 | $0.00011 | $0.00177 |
| Haiku 4.5 | $0.00005 | $0.00088 |
Grade A, and why
clone-update 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check the installed clone-team version against the latest release and update it
the correct way for how it was installed. This is a version-aware advisor,
not a blind git pull — overwriting a plugin-managed directory or a user's local
copy is a footgun, so detect the install type first and route accordingly.
Run-state and credentials are never at risk here: a run's .clone-team/
state and creds.local.json live in the cloned project's directory, not in the
skill install dir. Updating the skill does not go near them. Still, never copy
over or delete anything under a .clone-team/ path.
1. Find the latest version
Read the canonical version from the default branch on GitHub (no clone needed):
gh api repos/Varalix-Digitech-Solutions/clone-team/contents/.claude-plugin/plugin.json \
--jq '.content' 2>/dev/null | base64 -d | grep -m1 '"version"'
If gh is unavailable, fetch the same file over HTTPS:
https://raw.githubusercontent.com/Varalix-Digitech-Solutions/clone-team/main/.claude-plugin/plugin.json.
Call this LATEST.
2. Locate the local install and read its version
clone-team is installed in one of two shapes:
- Plugin — under the Claude Code plugins dir (e.g.
~/.claude/plugins/**/clone-team/, alongside a.claude-plugin/plugin.json). - Manual — the skill copied to
~/.claude/skills/clone-team/(often without the repo root, so.claude-plugin/plugin.jsonmay be absent).
Find it, then read its version from the nearest .claude-plugin/plugin.json if
present. If no manifest is present (a bare manual copy), say the local version is
unknown rather than guessing. Call this LOCAL.
3. Report status
Always tell the user plainly: LOCAL vs LATEST, and whether they're up to date,
behind, or unknown. Link the changelog:
https://github.com/Varalix-Digitech-Solutions/clone-team/blob/main/CHANGELOG.md.
If LOCAL == LATEST, stop here — nothing to do.
4. Route the update by install type
Plugin install → defer to the plugin manager. Do NOT mutate files.
Tell the user their install auto-updates through Claude Code's plugin system and
to update via the /plugin interface (manage the clone-team marketplace/plugin
there). A manual file copy into a plugin-managed directory will be reverted by the
manager and can corrupt its state — so don't do it.
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 · 72 lines · 53 tokens per session scan A caab455afd78
clone-update is a command published in the GitHub repository Varalix-Digitech-Solutions/clone-team (20 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 883 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.