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/knitli/toolshed/setupnpx skills add knitli/toolshed --skill setupgit clone --depth 1 https://github.com/knitli/toolshedWhat 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.00000 | $0.01481 |
| Opus 5 | $0.00000 | $0.00740 |
| Sonnet 5 | $0.00000 | $0.00296 |
| Haiku 4.5 | $0.00000 | $0.00148 |
Grade A, and why
setup scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl --fail-with-body -sS \ How it starts
The opening of the file, as written. The whole thing — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: codeweaver-setup version: 1.0.0 description: Reconfigure CodeWeaver settings (provider, credentials, repository) trigger: command commands:
- /codeweaver:setup
- /cw:setup author: Knitli Inc. license: MIT OR Apache-2.0
CodeWeaver Setup / Reconfiguration
You are helping a user reconfigure their CodeWeaver installation. This might be because:
- They want to switch embedding providers
- They need to update API credentials
- They're working on a different repository
- Initial setup failed and they're retrying
Your Goal
Guide the user through updating their CodeWeaver configuration. Be efficient since they've likely been through this before.
Setup Flow
1. Welcome & Context
Start with a brief greeting and ask what they want to change:
Let's reconfigure CodeWeaver.
What would you like to update?
1. Embedding provider (switch between Voyage/FastEmbed/other)
2. API credentials (update or add API key)
3. Repository/project path
4. All of the above (fresh setup)
Enter the number or describe what you need.
Based on their response, skip to the relevant section(s) below.
2. Embedding Provider Selection
If they want to change providers:
Current Options:
- Voyage AI (Voyage-4): Best-in-class code embeddings, requires API key
- FastEmbed (Local): Good quality, runs locally, no API key needed
Which provider would you like to use? (voyage/fastembed)
If switching TO Voyage from FastEmbed, proceed to step 3 (API key). If switching FROM Voyage to FastEmbed, offer to remove the old API key.
3. API Credentials
If they need to update credentials:
For Voyage AI:
Enter your Voyage AI API key (get one at https://voyage.ai):
Validation: Test the key before saving by assigning it inline so it doesn't need to be exported first:
VOYAGE_API_KEY="<key-provided-by-user>" \
curl --fail-with-body -sS \
-H "Authorization: Bearer ${VOYAGE_API_KEY}" \
-H "Content-Type: application/json" \
https://api.voyageai.com/v1/models
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 · 264 lines · 0 tokens per session scan A 2712622511c2
setup is a skill published in the GitHub repository knitli/toolshed (1 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,481 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
motherduck-build-cfa-app
Design a MotherDuck-backed customer-facing analytics app. Use for embedded analytics, multi-tenant SaaS reporting, or product analytics for external users -- whenever the decision depends on per-customer isolation, backend routing, service-account boundaries, read scaling, or Hypertenancy-style patterns.
motherduck-build-dashboard
Build a live MotherDuck dashboard as a Dive. Use when composing one shareable KPI, trend, and breakdown story over existing MotherDuck data, especially when the result should stay a saved workspace artifact rather than a full application.
motherduck-build-data-pipeline
Design an end-to-end MotherDuck data pipeline. Use for ETL/ELT workflows -- choosing raw, staging, and analytics boundaries, bulk ingestion paths, transformation sequencing, dlt/dbt integration, publication targets, or whether DuckLake is actually required.
motherduck-connect
Connect to MotherDuck from any application. Use when setting up database connectivity via the Postgres endpoint (recommended), pgduckdb, native DuckDB API, or JDBC. Covers connection strings, authentication, SSL, and environment variable configuration.
motherduck-create-dive
Create, edit, manage, share, or embed MotherDuck Dives — live React + SQL dashboards, charts, and data apps saved in the workspace. Use for any dashboard, chart, KPI display, or data visualization over MotherDuck data, and for Dive authoring mechanics such as getdiveguide, useSQLQuery, local preview, version history…
motherduck-create-flight
Create, schedule, run, and debug MotherDuck Flights — Python jobs that run on MotherDuck compute. Use whenever someone wants to create a flight, schedule a Python script or recurring job on MotherDuck, set up scheduled ingestion from Postgres, dlt sources, S3, BigQuery, Snowflake, or APIs, refresh aggregates or…