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 agents/yogasw/wick/providersgit clone --depth 1 https://github.com/yogasw/wickWhat 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.10066 |
| Opus 5 | $0.00000 | $0.05033 |
| Sonnet 5 | $0.00000 | $0.02013 |
| Haiku 4.5 | $0.00000 | $0.01007 |
Grade A, and why
providers 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 2d 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.
Each model's Add/Edit form has a collapsed **Advanced options** section with a **Custom headers** sub-section (also collapsed by default, alongside **Raw model config**). It accepts one `Key: Value` header per line — or How it starts
The opening of the file, as written. The whole thing — 446 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Providers
A provider type is an AI CLI: claude, codex, gemini (provider.go:36-40).
A provider instance is a configured copy of one. Multiple instances per type are supported — same claude binary, different env vars (e.g. two PATs).
::: info Source
Code: internal/agents/provider/.
UI handler: internal/tools/agents/providers.go.
:::
Why multi-instance
The use case is mundane: you have a personal Anthropic PAT and a work one. Both target the same claude binary. You want to pick which to use per session.
Each instance carries:
| Field | Notes | Source |
|---|---|---|
Type |
claude / codex / gemini. |
provider.go:34 |
Name |
Unique within type. Defaults to Type itself. Pick anything: work, personal, staging. |
provider.go:53 |
Binary |
Absolute path. Empty = let wick resolve via PATH + scan. | provider.go:54 |
ExtraArgs |
Appended to every spawn argv. | provider.go:55 |
Env |
Extra env vars. This is where ANTHROPIC_API_KEY goes for a per-instance PAT. |
provider.go:56 |
Disabled |
Toggle without deleting. | provider.go:57 |
UseAIRouter |
Route this instance's CLI through an embedded AI router instead of the provider's own API. claude/codex only. See AI Router provider integration. |
provider.go |
AIRouterProvider |
Which registered router to route through (9router, omniroute, …). Empty = default (9router). |
provider.go |
AIRouterModels |
Per-slot model IDs (e.g. opus → cc/claude-opus-4-6). Slots defined by the selected router. All optional. |
airouter.go |
AIRouterAPIKey |
Custom router API key, stored encrypted. Empty = the router's default credential. | airouter.go |
MemoryMaxMB |
Memory limit for this instance's agents, in MB, counting the whole process tree. 0 = follow the global agent_memory_max_mb. May exceed the global value — a memory ceiling is per-process, not a shared pool slot, so one heavy instance can be given more without making every other agent fatter. See Memory Guard. |
provider.go |
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.
- 2d ago First seen · 446 lines · 0 tokens per session scan A 098f4e8b60a0
providers is an agent published in the GitHub repository yogasw/wick (5 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 10,066 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 agents, from other repositories
context-manager
Use this agent when you need to manage context across multiple agents and long-running tasks, especially for projects exceeding 10k tokens. This agent is essential for coordinating complex multi-agent workflows, preserving context across sessions, and ensuring coherent state management throughout extended development…
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
Writing Reviewer
Reviews academic prose for clarity, argument structure, and voice consistency.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.