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 skills add itechmeat/llm-code --skill deps-devgit clone --depth 1 https://github.com/itechmeat/llm-codeWrote 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/itechmeat/llm-code/deps-dev)<a href="https://agentmods.dev/skills/itechmeat/llm-code/deps-dev"><img src="https://agentmods.dev/badge/skills/itechmeat/llm-code/deps-dev/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/itechmeat/llm-code/deps-dev"><img src="https://agentmods.dev/badge/skills/itechmeat/llm-code/deps-dev.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.00074 | $0.00528 |
| Opus 5.5 | $0.00030 | $0.00211 |
| Sonnet 5.5 | $0.00015 | $0.00106 |
| Haiku 4.5 | $0.00007 | $0.00053 |
Grade A, and why
deps-dev 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.
What it actually says
deps.dev (Skill Router)
This file is intentionally introductory.
Open the right note under references/ based on what you need.
Start here (fast)
- Need the latest/default version of a known package? Read:
references/latest-version.md. - Handling huge version lists or truncated responses? Read:
references/large-responses.md. - Not sure how to format/normalize package names per ecosystem? Read:
references/naming-and-encoding.md. - Need endpoint shapes and fields to parse, including deprecation flags (
isDeprecated/deprecatedReason), PyPIprojectStatus, or resolved NuGet/Maven requirements? Read:references/api.md.
Primary recipe (one request)
Goal: given {system, packageName}, return the default/latest version.
- Call GetPackage:
GET https://api.deps.dev/v3/systems/{SYSTEM}/packages/{PACKAGE} - Parse
versions[]and select the item withisDefault=true.
If isDefault is missing for all versions, stop and ask for an explicit selection rule (e.g., include pre-releases or not) instead of guessing.
isDefault does not imply the version is safe to recommend: also check isDeprecated/deprecatedReason on that version (see references/api.md) before suggesting it.
Critical prohibitions
- Do not guess the “latest” version by string sorting.
- Do not output placeholder or “approximate” versions; always wait for API data.
- Do not parse large JSON via
grepor manual truncation; use a JSON parser (jq/Python/Node). - Do not silently fall back when
isDefaultis missing; ask for the desired rule. - Do not paste large verbatim chunks from docs; summarize.
- Do not assume auth or rate limits; treat them as unspecified unless you have evidence.
Links
What ships with it
5 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 · 46 lines · 74 tokens per session scan A aae003ac0d93
deps-dev is a skill published in the GitHub repository itechmeat/llm-code (24 stars, last pushed 24d ago), licensed MIT. It adds 74 tokens to every session and 528 once invoked, about $0.0003 per session on Opus 5.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 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…
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.