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/rahmanef63/si-coder-agent/sc-helpnpx skills add rahmanef63/si-coder-agent --skill sc-helpgit clone --depth 1 https://github.com/rahmanef63/si-coder-agentWhat 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.00085 | $0.01689 |
| Opus 5 | $0.00043 | $0.00844 |
| Sonnet 5 | $0.00017 | $0.00338 |
| Haiku 4.5 | $0.00009 | $0.00169 |
Grade A, and why
sc-help 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 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.
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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sc-help — SI-Coder quick reference
sc — the provider console (new)
| Command | What it answers |
|---|---|
sc providers |
which providers are configured, and what is missing |
sc providers show <id> |
every var for one provider + where to get it |
sc providers set <id> |
re-enter / rotate one provider's credentials |
sc providers rm <id> --yes |
drop its vars from the ~/.bashrc managed block |
sc setup [--target t] |
interactive wizard for whatever is missing |
sc doctor [--target t] |
live — calls each real API and names what it reached |
sc preflight --target t |
the gate /sc-all runs before touching anything |
providers = configured (presence + format). doctor = actually works (real API call).
| sc user | profiles, and which folder uses which |
| sc user which | why this directory resolves to that profile |
| sc user add <n> [--from-shell] | create a profile (optionally import current env) |
| sc user map <folder> <n> | bind a folder + children to a profile |
| sc env / sc run -- <cmd> | apply the resolved profile to a shell / one command |
Multiple identities on one machine: credentials in ~/.config/si-coder/profiles/<n>.env,
the folder map in ~/.config/si-coder/sc.md. Longest matching path wins. A profile
overrides the shell and removes credentials it does not own — --no-profile opts out.
Run sc with no arguments for an arrow-key menu. Any command that picks a provider or a
target opens a list instead of asking you to type the name: ↑/↓ move, Space toggle
(multi-select), a all/none, Enter confirm, Esc cancel.
One-shot cheat sheet for the /sc-* deploy bundle. Show this, then route the user to the
specific skill. Not a mode — display and stop.
Deploy targets (/sc-all --target …)
Same flow shape everywhere: GitHub → backend → frontend → DNS → verify. Pick by where things run.
--target |
Frontend | Backend | Env needed | Pick when |
|---|---|---|---|---|
dokploy (default) |
Dokploy app (your VPS) | Convex self-hosted (compose on Dokploy) | DOKPLOY_* + GITHUB_TOKEN |
own the box, $0 marginal, full control |
hybrid |
Dokploy app (your VPS) | Convex Cloud (managed) | DOKPLOY_* + GITHUB_TOKEN + CONVEX_DEPLOY_KEY |
app on your box, DB managed — no compose to babysit |
vercel |
Vercel (managed edge) | Convex Cloud (managed) | VERCEL_TOKEN + GITHUB_TOKEN + CONVEX_DEPLOY_KEY |
managed edge, no VPS to babysit |
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 · 94 lines · 85 tokens per session scan A 37c2f6877294
sc-help is a skill published in the GitHub repository rahmanef63/si-coder-agent (14 stars, last pushed 5d ago), licensed MIT. It adds 85 tokens to every session and 1,689 once invoked, about $0.0004 per session on Opus 5. 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-30.
Other skills, from other repositories
convex-self-hosting
Integrate Convex static self hosting into existing apps using the latest upstream instructions from get-convex/self-hosting every time. Use when setting up upload APIs, HTTP routes, deployment scripts, migration from external hosting, or troubleshooting static deploy issues across React, Vite, Next.js, and other…
setup-convex-worktrees
Set up, repair, or explain isolated Convex development deployments for Git worktrees and coding agents, including per-worktree env bindings, temporary deployment creation, baseline data seeding, frontend port isolation, and AGENTS.md guardrails. Use when separate checkouts are clobbering one shared Convex dev…
garage
Operate Joel's Garage S3-compatible object storage on three-body. Use for Garage, Convex Garage, Garage S3, three-body Garage, port 39100, Garage buckets, and MinIO-to-Garage migration.
deployhq
Deploy code, manage servers, and automate infrastructure via the DeployHQ CLI (dhq). Use when the user wants to deploy, check deployment status, manage projects/servers, or interact with the DeployHQ platform.
Convex Cron Jobs
Scheduled function patterns for background tasks including interval scheduling, cron expressions, job monitoring, retry strategies, and best practices for long-running tasks.
kagent-dev
Development guide for kagent's v1alpha3 Harness and AgentTemplate CRDs, AgentInstance gRPC control plane, upstream A2A integration, Substrate runtime provisioning, tests, generation, and PR workflow. Use for any implementation, debugging, review, or CI task in the kagent repository.