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/yogasw/wick/connector-modulenpx skills add yogasw/wick --skill connector-modulegit clone --depth 1 https://github.com/yogasw/wickWrote 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/yogasw/wick/connector-module)<a href="https://agentmods.dev/skills/yogasw/wick/connector-module"><img src="https://agentmods.dev/badge/skills/yogasw/wick/connector-module.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.00165 | $0.09326 |
| Opus 5 | $0.00082 | $0.04663 |
| Sonnet 5 | $0.00033 | $0.01865 |
| Haiku 4.5 | $0.00016 | $0.00933 |
Grade A, and why
connector-module 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **curl / manual** defs: sections are stored and editable in the builder (named sections + drag-drop ops between them). How it starts
The opening of the file, as written. The whole thing — 605 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Connector Module — wick core (upstream)
Scope: this skill is for connectors that ship inside wick itself — modules under
internal/connectors/registered frominternal/connectors/registry.go::RegisterBuiltins(). If you are building a connector in a downstream project (a scaffold generated fromtemplate/), use the downstream skill attemplate/.claude/skills/connector-module/SKILL.md— paths, registration site, and verification differ.
Activate this skill whenever the user touches a connector in the wick lab binary or the connector framework itself — creating, improving, fixing, refactoring, or adding operations. When editing an existing connector, audit it against the rules below and bring it up to spec as part of the change.
Mental model
A connector wraps one external API for LLM consumption.
- One
Modulecarries one sharedConfigsstruct (URL, token, ...) and NOperations(query,list_repos,create_issue, ...), grouped into categories (titled sections). Module.Operationsis a[]connector.Category— eachCategory{Title, Description, Ops}owns its operations. The admin detail page renders one card per category. Code that needs the flat op list callsModule.AllOps(); an op's owning section isModule.CategoryOf(opKey). There is noOperation.Categoryfield — the section owns the grouping.- Each
Operationhas its own typedInputstruct (turned into the MCP JSON Schema) and its ownExecuteFunc. - An admin can create many rows per definition at runtime; each row carries its own credential values, label, and tags. Same Go code, different rows = different (env, team, account).
- LLMs do not see N×M static tools. The MCP server exposes a fixed meta surface (
wick_list,wick_search,wick_get,wick_execute); each (row × operation) pair is addressed by an opaquetool_idof the formconn:{connector_id}/{op_key}.
The full design lives in internal/planning/archive/connectors-design.md. This skill is the operational summary; that document is the source of truth for any architectural question.
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.
- 3d ago First seen · 605 lines · 165 tokens per session scan A 74dd14162009
connector-module is a skill published in the GitHub repository yogasw/wick (5 stars, last pushed 6d ago), licensed MIT. It adds 165 tokens to every session and 9,326 once invoked, about $0.0008 per session on Opus 5. 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
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.
golden-rss
Use when testing the rss golden build.
overleaf-sync
Two-way sync between a local paper directory and an Overleaf project, so ARIS audit/edit workflows stay on the local copy while collaborators edit in the Overleaf web UI. Use when user says "同步 overleaf", "overleaf sync", "推送到 overleaf", "connect overleaf", "Overleaf 桥接", "pull overleaf", "push overleaf", or wants to…
omh-code-review
This is a Hermes-native code-review workflow skill.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
workflow-builder
Load before calling build-workflow. Default path for all single-workflow work: new one-off workflows, existing-workflow edits, verification repairs, and workflow-local data tables. Write or edit a workspace source file, run workflow-sdk validate via workspaceexecutecommand, then call build-workflow with filePath. When…