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/source-controlgit 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.02083 |
| Opus 5 | $0.00000 | $0.01042 |
| Sonnet 5 | $0.00000 | $0.00417 |
| Haiku 4.5 | $0.00000 | $0.00208 |
Grade A, and why
source-control 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.
How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Source Control (Git) Panel
The Source Control panel is a VSCode-style SCM sidebar mounted on the session detail page (/tools/agents/sessions/<id>). It lets you stage, commit, push, pull, view diffs, and browse history for any git repositories inside the session's working directory — without leaving the chat.
::: info Source
Backend: internal/agents/scm/ — git.go (git shell-outs), scan.go (multi-repo discovery).
Handler: internal/tools/agents/scm.go, scm_watch.go (SSE watcher).
Frontend SPA: fe/agents/scm/ — Svelte 5, Monaco editor, mounted as an island into the session page.
Endpoints: /tools/agents/api/sessions/{id}/git/*.
:::
::: warning Prerequisite
git must be on PATH on the host running wick. The panel shells out to the real git binary — it does not bundle one. Existing SSH / PAT credentials and ~/.gitconfig settings apply as-is.
:::
Opening the panel
The session detail page has a right-edge rail with three tabs: Context, Process, and Source. Click Source (or the tab label) to open the Source Control panel.
The panel opens as a slide-over overlay by default. To dock it, click the pin icon in the panel header. When pinned, the chat content area reflows to the left to make room — the panel does not overlap it.
| State | Behaviour |
|---|---|
| Unpinned | Overlay on top of the chat; click outside or press Esc to close. |
| Pinned | Docked alongside the chat; chat content pushes left. |
Pin state and panel width are persisted in localStorage. The panel is resizable: drag the left handle to any width between 240 px and 640 px (default 260 px).
Layout (full mode)
In full mode the panel uses a two-column layout:
- Left column (220 px) — file list grouped into Staged and Changes sections, commit message input, and branch bar at the bottom.
- Right column (flex) — Monaco diff editor as the primary surface. The first changed file is selected automatically on load.
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 · 161 lines · 0 tokens per session scan A 8d6d1747c42b
source-control 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 2,083 tokens. 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 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.