Borrowing it
Nothing to install: this file belongs to mazumba/opencode-dockerized. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mazumba/opencode-dockerized/main/.opencode/config/skills/clonedeps/SKILL.mdgit clone --depth 1 https://github.com/mazumba/opencode-dockerizedWrote 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/skills/mazumba/opencode-dockerized/clonedeps)<a href="https://agentmods.dev/skills/mazumba/opencode-dockerized/clonedeps"><img src="https://agentmods.dev/badge/skills/mazumba/opencode-dockerized/clonedeps/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mazumba/opencode-dockerized/clonedeps"><img src="https://agentmods.dev/badge/skills/mazumba/opencode-dockerized/clonedeps.svg" alt="Reviewed on agentmods" width="80" 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.00076 | $0.02009 |
| Opus 5.5 | $0.00030 | $0.00804 |
| Sonnet 5.5 | $0.00015 | $0.00402 |
| Haiku 4.5 | $0.00008 | $0.00201 |
Grade A, and why
clonedeps 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 1mo 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.
This is a copy
86% identical to clonedeps — 77 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clonedeps Skill
You help users make a small set of important dependency source repositories locally readable to OpenCode.
This is a workflow skill, not a command wrapper. Do not use a helper script for
dependency detection, ref validation, cloning, status, or cleanup. The
orchestrator and @librarian do the repo-specific thinking; the orchestrator
performs the approved filesystem/git operations directly.
Workflow
Step 1: Check Existing State
First check whether .slim/clonedeps.json exists.
If it exists:
- Read it before asking librarian for a new plan.
- Check whether each listed
pathexists under.slim/clonedeps/repos/. - Reuse existing cloned repos when they already satisfy the user's task.
- Only ask librarian for new recommendations if the existing manifest is missing, stale, or insufficient for the current task.
Do not rescan/re-plan from scratch when the manifest already has useful entries.
Step 2: Ask Librarian for the Clone Plan
Delegate dependency discovery and source resolution to @librarian.
Use this prompt:
Understand this project first, then recommend remote source repos that would
help a developer work on it.
Read enough of the current repo to understand:
- what the project does
- its main architecture
- the important integration points
- what external systems or libraries it depends on in practice
Think like a developer trying to debug or extend this project.
Which remote repositories, if cloned locally, would actually help understand the
codebase or solve likely implementation/debugging tasks?
Do not make a dependency dump. Most dependencies are not worth cloning.
Recommend a repo only when its source code would be more useful than docs or the
current repo alone.
For each recommendation, include:
- repo name
- repo URL
- suggested ref/tag/commit if known
- why cloning this source would help
- when it would be useful
- caveats
Also include:
- current-repo files/folders to inspect first
- repos/dependencies you considered but would not clone
Keep it small. Prefer 0–3 strong recommendations over 5 weak ones. If nothing
clearly needs cloning, say so.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 238 lines · 76 tokens per session scan A d7c99f6dcb68
clonedeps is a skill published in the GitHub repository mazumba/opencode-dockerized (6 stars, last pushed 2d ago), licensed MIT. It adds 76 tokens to every session and 2,009 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to clonedeps, differing in 77 lines, and is treated as a copy.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.