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 skills/git-pkgs/skills/listnpx skills add git-pkgs/skills --skill listgit clone --depth 1 https://github.com/git-pkgs/skillsWhat 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.00042 | $0.00578 |
| Opus 5 | $0.00021 | $0.00289 |
| Sonnet 5 | $0.00008 | $0.00116 |
| Haiku 4.5 | $0.00004 | $0.00058 |
Grade A, and why
list 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 yesterday.
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
List and Search Dependencies
Query the current state of dependencies in a project.
Commands
List all dependencies at HEAD:
git-pkgs list
Options:
--commit=REF- list at a specific commit-e ECO- filter by ecosystem-m PATH- filter by manifest file-t TYPE- filter by dependency type (runtime, development)-f json- JSON output
Show dependency tree (grouped by manifest and type):
git-pkgs tree
Resolve the actual dependency graph by running the local package manager (assumes deps are installed):
git-pkgs resolve
git-pkgs resolve -f json
Search by name pattern:
git-pkgs search lodash
git-pkgs search "react-*"
Find where a package is declared (file path, line number, content):
git-pkgs where lodash
Open a package's source in your editor:
git-pkgs browse lodash
Show registry URLs (registry page, download, docs, PURL):
git-pkgs urls lodash
git-pkgs urls pkg:npm/[email protected]
Show maintainers for each dependency:
git-pkgs maintainers
git-pkgs maintainers --single # only packages with one maintainer
Show funding links for dependencies:
git-pkgs funding
git-pkgs funding --missing
Show lockfile integrity hashes and detect drift:
git-pkgs integrity
Manage notes on packages:
git-pkgs notes add pkg:npm/lodash "reviewed for security"
git-pkgs notes list pkg:npm/lodash
When to use
- When the user asks what dependencies are installed
- When looking for a specific package in the project
- When checking which manifest file declares a dependency
- When exploring the dependency structure
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.
- yesterday First seen · 87 lines · 42 tokens per session scan A f46f1b44fdcf
list is a skill published in the GitHub repository git-pkgs/skills (1 stars, last pushed 12d ago), licensed MIT. It adds 42 tokens to every session and 578 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-31.
Other skills, from other repositories
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
mintlify-preview
Run the public Mintlify product docs site locally for live preview. Use when previewing or iterating on docs under docs/ (.mdx/.md pages, docs.json nav), or when the user says "start the docs", "run mintlify", "preview the docs site".
openclaw-design-system
Compatibility alias for existing OpenClaw installations that now applies Carapace semantic tokens, themes, shared CSS foundations, consumer adapters, and established local primitives.
traceway-setup
Analyze and instrument repositories for Traceway observability. Use when the user wants to plan, add, migrate, or verify Traceway or OpenTelemetry monitoring for backend, browser, full-stack, mobile or iOS, or AI-agent software, including project topology and user-approved setup-plan creation. Backends use OTLP/HTTP…