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/control-room/si-codernpx skills add rahmanef63/control-room --skill si-codergit clone --depth 1 https://github.com/rahmanef63/control-roomWhat 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.00051 | $0.03479 |
| Opus 5 | $0.00026 | $0.01740 |
| Sonnet 5 | $0.00010 | $0.00696 |
| Haiku 4.5 | $0.00005 | $0.00348 |
Grade A, and why
si-coder 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.
curl -X POST https://api-<appname>.<your-domain>/api/update_environment_variables \ How it starts
The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SI Coder Auto Deploy
This skill automates the entire lifecycle of creating a GitHub repository and deploying full-stack apps to a Dokploy server.
CORE MANDATES FOR THE AI (LEARNED LESSONS)
To guarantee Zero Human Involvement (the user just wants to receive the final working URL):
- Self-Hosted Convex by Default: NEVER use Clerk unless explicitly asked. ALWAYS use
@convex-dev/auth. ALWAYS include adocker-compose.ymlfor self-hosting Convex alongside the frontend. - Build Safety: Do NOT run
npx convex codegeninside theDockerfile. You MUST generate the types locally (npx convex dev --once) and commit theconvex/_generatedfolder to Git before deploying. - No Prompts / Dependency Hell: Always use
npm install --yes --legacy-peer-deps. If a scaffolded template is too complex (bloated), wipe it and start fresh withnpx create-next-appto avoid endless TypeScript errors. - Exact Cloning: If asked to clone a website, you MUST replicate its actual layout and structure, not just build a generic admin dashboard. Fetch the website to understand its structure.
- Dokploy Idempotency: The deployment script handles existing apps, composes, and domains safely. Do NOT delete or recreate existing domains if Dokploy rejects them (it means they are already configured).
- Convex Admin Key Sync: When generating or rotating a self-hosted Convex admin key, immediately update the Dokploy Compose environment and the repo's local env file so they stay in sync. Use the project's actual env name for that template or app, and do not invent a second secret name.
- Clerk MCP for Clerk Apps: If a target project already uses Clerk, preserve it, do not swap it to
@convex-dev/auth, and use Clerk MCP (clerkathttps://mcp.clerk.com/mcp) for SDK snippets and integration patterns.
Pre-requisites
- Dokploy Credentials: Environment variables
DOKPLOY_API_URLandDOKPLOY_API_KEY(usually stored in~/.bashrc). - GitHub Credentials: A GitHub Personal Access Token (PAT) with repository creation permissions, stored in
GITHUB_TOKENenvironment variable. - Hostinger Credentials:
HOSTINGER_API_TOKEN(optional but recommended for DNS automation). - SSH Keys: The machine must have SSH access to GitHub (
[email protected]) configured for pushing code.
What ships with it
2 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.
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 · 236 lines · 51 tokens per session scan A 68cadbf48359
si-coder is a skill published in the GitHub repository rahmanef63/control-room (19 stars, last pushed 2d ago), licensed MIT. It adds 51 tokens to every session and 3,479 once invoked, about $0.0003 per session on Opus 5. 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-30.
Other skills, from other repositories
adapter-aws-lambda
Deploy tRPC on AWS Lambda with awsLambdaRequestHandler() from @trpc/server/adapters/aws-lambda for API Gateway v1 (REST, APIGatewayProxyEvent) and v2 (HTTP, APIGatewayProxyEventV2), and Lambda Function URLs. Enable response streaming with awsLambdaStreamingRequestHandler() wrapped in awslambda.streamifyResponse().…
adapter-fetch
Deploy tRPC on WinterCG-compliant edge runtimes with fetchRequestHandler() from @trpc/server/adapters/fetch. Supports Cloudflare Workers, Deno Deploy, Vercel Edge Runtime, Astro, Remix, SolidStart. FetchCreateContextFnOptions provides req (Request) and resHeaders (Headers) for context creation. The endpoint option…
portaljs-deploy
Deploy a PortalJS portal to PortalJS Arc — Datopian-managed static hosting on Cloudflare. Builds a static export, uploads it, and returns a live SLUG.arc.portaljs.com URL. One command, one target. Use when a portal is ready to publish or redeploy to a live URL.
prepare-cloudflare-production-deployment
Source-of-truth runbook for preparing this Vinext Cloudflare Workers SaaS template for production deployment. Use when setting up or auditing Cloudflare MCP resources, wrangler.jsonc bindings, Worker secrets, Turnstile, Email Sending, GitHub Actions secrets/variables, or GitHub CLI deployment wiring for this…
release-beta
Publish the next AlphaClaw beta and always update the Railway beta template pin to the exact released beta version.
system-design-resilience-ops
Make a design survivable and operable: eliminate single points of failure, pick failover topology, set RPO/RTO, define readiness signals and observability, choose a deployment and rollback strategy. Use when reviewing availability, planning DR, or deciding rollout mechanics.