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-reportgit 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-report)<a href="https://agentmods.dev/commands/varalix-digitech-solutions/clone-team/clone-report"><img src="https://agentmods.dev/badge/commands/varalix-digitech-solutions/clone-team/clone-report.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.00045 | $0.00365 |
| Opus 5 | $0.00023 | $0.00182 |
| Sonnet 5 | $0.00009 | $0.00073 |
| Haiku 4.5 | $0.00005 | $0.00036 |
Grade A, and why
clone-report 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
Render and surface the results-analysis report for a clone-team run.
- Resolve the project dir: use
$ARGUMENTSif given, else the current working directory. The results live in<projectDir>/.clone-team/report.json. - If
report.jsondoes not exist, say so. It is written by the Tester (oneappend-roundper round) and finalized by the Manager — so it appears once a run has produced at least one tested section. Offer/clone-statusfor lifecycle state instead. - Render the HTML from the JSON source of truth:
node <clone-team-skill>/scripts/report.mjs render --dir <projectDir>(the skill usually lives at~/.claude/skills/clone-team). This writes<projectDir>/.clone-team/report.html. - Open
report.htmlfor the user (e.g.cmd.exe /c start "" "<path>"on Windows,openon macOS,xdg-openon Linux). Print the absolute path too. - For a quick text summary, also run
node <clone-team-skill>/scripts/report.mjs json --dir <projectDir>and report in a few lines: final verdict, sections passed / flagged, the lowest-scoring section, and any outstanding blocker/major issues.
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 · 27 lines · 45 tokens per session scan A ccad2588f6b5
clone-report 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 365 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
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.