Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/rahmanef63/si-coder-agentnpx agentmods add skills/rahmanef63/si-coder-agent/sc-onboardingWrote 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/rahmanef63/si-coder-agent/sc-onboarding)<a href="https://agentmods.dev/skills/rahmanef63/si-coder-agent/sc-onboarding"><img src="https://agentmods.dev/badge/skills/rahmanef63/si-coder-agent/sc-onboarding/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/rahmanef63/si-coder-agent/sc-onboarding"><img src="https://agentmods.dev/badge/skills/rahmanef63/si-coder-agent/sc-onboarding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 7 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 161 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Excessive Agency · line 18 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Rogue Agent · line 29 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Excessive Agency · line 37 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 40 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Rogue Agent · line 137 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 161 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.1 | $0.00067 | $0.03514 |
| Opus 5.5 | $0.00027 | $0.01406 |
| Sonnet 5.5 | $0.00013 | $0.00703 |
| Haiku 4.5 | $0.00007 | $0.00351 |
Grade A, and why
sc-onboarding 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 1mo 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sc-onboarding — Guided credential setup
Language
Keep durable instructions in English. Reply in the user's language unless they request another language.
Agent secret boundary: never ask the user to paste an API key/token/password into chat, an MCP/function argument, or argv. Resolve
user → provider → connectionfirst. OAuth stays in the external connected-account flow; a direct new/rotated secret is entered withsc user credential-set <user> <provider> <KEY> --connection <alias>in the hidden terminal. Consume withsc run [--connection provider=alias] -- <cmd>.
Use this skill when the user is setting up si-coder-agent for the first time, or after they install a new /sc-* domain skill that needs new credentials.
Non-technical default UX — mandatory
SI-Coder is primarily for people who want a working web app, not an infrastructure lesson. Lead with the outcome, hide the plumbing.
A valid user request can be as simple as:
"Create a salon booking app and put it on my domain."
From that sentence, the agent should normally choose the stack, database/data service, hosting route, repository strategy, deployment method, domain records, and verification approach itself.
Rules:
- Speak in goals: "publish the app", "connect the account", "connect the domain", "store the app data". Do not lead with terms such as environment variable, DNS record, deploy key, compose, container, build pipeline, or provider routing.
- One user action at a time. Never dump a setup checklist when only one permission/account connection blocks progress.
- Do not ask users to choose technology unless they explicitly care. Choose sensible defaults and keep the technology name in optional technical details.
- Do not ask a question that tools/repo state can answer. Inspect first, then ask only the unresolved product/domain/account decision.
- Credentials are framed as permissions, not secrets. Say "I need permission to use the email service" first. Then show the official create/connect action, where access is stored, and what SI-Coder will do next. Put env-key names and terminal commands under optional technical details unless the user must run the command.
- Never ask the user to copy values between services when a connector/server-side flow can do it safely.
- Progress is product-oriented:
Build the app → Prepare data → Publish → Connect domain → Verify, not internal provider phases. - Every completion message must state what is now working and then offer exactly one
[rekomendasi]next step. - Technical users can ask for "technical details",
--technical, JSON, or provider-specific skills. Do not force those details on everyone else.
What ships with it
15 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.
- lib/onboarding-domains.js 2.4 KB runs code
- scripts/scan-env.js 8.5 KB runs code
- steps/cf.md 857 B
- steps/clerk.md 1.2 KB
- steps/composio.md 1.7 KB
- steps/convex-cloud.md 2.5 KB
- steps/convex.md 662 B
- steps/dokploy.md 905 B
- steps/github.md 2.4 KB
- steps/hostinger.md 1.3 KB
- steps/resend.md 1.6 KB
- steps/stripe.md 1.0 KB
- steps/supabase.md 1.1 KB
- steps/sync.md 2.8 KB
- steps/vercel.md 823 B
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.
- 1mo ago Changed · +52 lines · +3 tokens per session scan D → A 72f847d67a1e
- 1mo ago First seen · 207 lines · 64 tokens per session scan D 22d2a7a50a9b
sc-onboarding is a skill published in the GitHub repository rahmanef63/si-coder-agent (13 stars, last pushed 3d ago), licensed MIT. It adds 67 tokens to every session and 3,514 once invoked, about $0.0003 per session on Opus 5.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-http-actions
External API integration and webhook handling including HTTP endpoint routing, request/response handling, authentication, CORS configuration, and webhook signature validation.
convex-migrations
Schema migration strategies for evolving applications including adding new fields, backfilling data, removing deprecated fields, index migrations, and zero-downtime migration patterns.
convex-security-audit
Deep security review patterns for authorization logic, data access boundaries, action isolation, rate limiting, and protecting sensitive operations.
avoid-feature-creep
Prevent feature creep when building software, apps, and AI-powered products. Use this skill when planning features, reviewing scope, building MVPs, managing backlogs, or when a user says "just one more feature." Helps developers and AI agents stay focused, ship faster, and avoid bloated products.
convex-agents
Building AI agents with the Convex Agent component including thread management, tool integration, streaming responses, RAG patterns, and workflow orchestration.
convex-component-authoring
How to create, structure, and publish self-contained Convex components with proper isolation, exports, and dependency management.