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/ozankasikci/sol-skill/solnpx skills add ozankasikci/sol-skill --skill solgit clone --depth 1 https://github.com/ozankasikci/sol-skillWrote 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/ozankasikci/sol-skill/sol)<a href="https://agentmods.dev/skills/ozankasikci/sol-skill/sol"><img src="https://agentmods.dev/badge/skills/ozankasikci/sol-skill/sol.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.00048 | $0.04179 |
| Opus 5 | $0.00024 | $0.02090 |
| Sonnet 5 | $0.00010 | $0.00836 |
| Haiku 4.5 | $0.00005 | $0.00418 |
Grade B, and why
sol scanned grade B 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Validate any key with `codex exec --strict-config`, which errors on unrecognized fields — note that `[projects."<path>"]` sections in `~/.codex/config.toml` accept only `trust_level`, so sandbox settings cannot be scoped How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sol — Sol implements, Claude reviews
Task: $ARGUMENTS
Role split (strict): Claude never edits production code in this flow. Claude plans, briefs Sol, reviews the real diff, and directs corrections. GPT-5.6 Sol (via Codex CLI) makes all code changes and runs tests.
Task routing: Implementation tasks follow phases 1–5. If the task is research or investigation (no code changes requested), the planner model does the research itself with its own tools — do NOT invoke Sol, unless the user explicitly names Sol as the researcher ("sol research…", "have sol research", "ask sol"). In that case skip to Research mode at the bottom.
Parallel routing: If — and only if — the user names a worker count (--workers N,
or "use 3 workers"), follow references/parallel-flow.md instead of phases 2–5. Never
infer parallelism from a request that merely looks like several tasks; the trigger is
the number the user typed, not a judgment about the work. --workers 1 is the normal
flow below.
| Setting | Default | Meaning |
|---|---|---|
--workers N |
— | Requested worker count for this run, capped by the ceiling below; its presence engages parallel mode |
SOL_MAX_WORKERS |
3 |
Ceiling on worker count — caps --workers and is the count used when --workers is absent; exceeding it is refused, never clamped |
SOL_WORKTREE_SETUP |
unset | Command run in each fresh worktree (npm ci, uv sync) |
SOL_EFFORT |
high |
Reasoning effort for workers. high verifies its own work when a compiler and tests are in the loop, and stalls are effort-correlated (openai/codex#24260, #23807) — an xhigh stall burns the whole first-event budget before anything happens. Raise to xhigh for algorithmically hard briefs |
SOL_FIRST_EVENT_TIMEOUT |
300 |
Parallel mode: seconds a worker may sit with nothing but thread/turn bookkeeping in its event log before it is stall-killed |
SOL_IDLE_TIMEOUT |
600 |
Parallel mode: seconds without any new event after real work has started before a worker is stall-killed |
SOL_COMMAND_TIMEOUT |
1800 |
Parallel mode: seconds an in-flight command may produce nothing before the worker is stall-killed — bounds the exemption that lets long silent builds run |
SOL_WORKER_TIMEOUT |
off | Parallel mode: optional absolute per-worker cap in seconds. Off by default — a task's duration is not predictable, so any constant kills productive workers; the budgets above bound silence instead |
SOL_STALL_RETRIES |
1 |
Parallel mode: automatic relaunches of a stalled worker, each a fresh session one effort step lower (xhigh → high → medium → low) |
SOL_SANDBOX |
workspace-write |
Sandbox policy passed as -s. danger-full-access for a toolchain the sandbox cannot reach at all (Docker). Removes all confinement; the run warns on stderr. Cannot be set via SOL_CODEX_CONFIG |
SOL_CODEX_CONFIG |
unset | Extra -c key=value overrides, space separated, applied to every codex invocation the launcher makes. See Sandboxed toolchains below. Values must not contain spaces |
Task tracking: If harness task tools are available, call TaskCreate at the start (short title from the request, status in_progress), TaskUpdate once per phase transition (planning → Sol implementing → reviewing → corrections), and TaskUpdate to completed in the final report — or leave it in_progress with a note if blocked. Keep updates to one line; skip entirely if the tools are unavailable.
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/brief-template.md 5.8 KB
- references/parallel-flow.md 12 KB
- scripts/check-codex.sh 6.7 KB runs code
- scripts/sol-parallel.sh 47 KB runs code
- scripts/sol-watch.py 12 KB runs code
- scripts/tests/fixture-crash.jsonl 656 B
- scripts/tests/fixture-refactor.jsonl 3.5 KB
- scripts/tests/test_sol_parallel.py 95 KB runs code
- scripts/tests/test_sol_watch.py 5.4 KB runs code
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 Changed · +3 lines · +4 tokens per session b4b40536e297
- 5d ago First seen · 174 lines · 44 tokens per session scan B 18112cc54863
sol is a skill published in the GitHub repository ozankasikci/sol-skill (27 stars, last pushed 2d ago), licensed MIT. It adds 48 tokens to every session and 4,179 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
supervisor
Autonomous multi-agent quality supervisor and release gate. Use when a user wants the best possible result, asks for rigorous review, or when a substantive answer/deliverable should be challenged before release. Decomposes the task, fans out independent subagents, uses specialist and adversarial judges, verifies…
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
local-frontend-check
Smoke-test or verify UI behaviour on the local Jarvis Registry frontend running at http://localhost/gateway. Use for manual regression checks, bug-fix verification, and end-to-end confirmation of specific flows without running the automated test suite.
ppt-review
Read this skill only after current officereview structural output and relevant rendered images exist. Do not use source code, a tool success flag, or the first-slide preview as a substitute for deck evidence.
package-installer
Install third-party open-source projects (a GitHub URL or a local git directory the user provides) as external packages. The project is cloned verbatim into the per-user packages directory — never edit, normalize, or reorganize its files.