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 skills add ericrisco/rsc-harness --skill railwaygit clone --depth 1 https://github.com/ericrisco/rsc-harnessWrote 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/ericrisco/rsc-harness/railway)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/railway"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/railway/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/ericrisco/rsc-harness/railway"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/railway.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Excessive Agency · line 55 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.
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.00087 | $0.03037 |
| Opus 5 | $0.00044 | $0.01519 |
| Sonnet 5 | $0.00017 | $0.00607 |
| Haiku 4.5 | $0.00009 | $0.00304 |
Grade A, and why
railway 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 9d 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.
bash <(curl -fsSL railway.com/install.sh) # shell installer How it starts
The opening of the file, as written. The whole thing — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Railway — ship a repo to a managed PaaS
Railway is an opinionated PaaS: connect a GitHub repo or run railway up, and it builds your
code (Railpack by default, or your Dockerfile), runs the container, networks it, and hands you a
domain. You manage services, environments, variables, volumes, and databases — not servers,
not an OS. This skill makes you fast and correct on Railway's specific surface, not generic
deploy theory.
repo / `railway up` → Railpack (or Dockerfile) build → container runs (binds 0.0.0.0:$PORT)
→ variables + reference vars injected → private net (*.railway.internal) + public domain
Is Railway the right target?
Settle this before touching config. If the user named the platform, honor it and route.
| Want | Use | Why / route |
|---|---|---|
| Push a repo, get a built+running app with zero ops | Railway (this skill) | Managed PaaS, Railpack build, by-the-minute billing |
render.yaml Blueprint, free static sites, their dashboard model |
render |
Different PaaS — route to the render skill |
fly.toml, Firecracker microVMs, fly machine, multi-region edge |
fly-io |
Railway has no fly machine equivalent — route to fly-io |
| Self-host the PaaS on your own Hetzner/DO box | coolify |
Railway is fully managed; Coolify is BYO-server |
| Raw VPS, you manage the OS | hetzner / digitalocean |
IaaS, not PaaS |
| Platform-agnostic release strategy (rolling, blue-green theory) | deployment |
This skill is Railway mechanics, not strategy |
The 60-second path
# Install the CLI (pick one). npm form needs Node 16+.
brew install railway # macOS
npm i -g @railway/cli # any Node 16+ host
bash <(curl -fsSL railway.com/install.sh) # shell installer
railway login # opens browser; for CI use RAILWAY_TOKEN instead (no login)
railway init # create a NEW project from this dir, OR:
railway link # link this dir to an EXISTING project/service
railway up # build + deploy the current dir; streams build/deploy logs
What ships with it
5 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.
- 9d ago First seen · 246 lines · 87 tokens per session scan A a258732503c3
railway is a skill published in the GitHub repository ericrisco/rsc-harness (82 stars, last pushed 2d ago), licensed MIT. It adds 87 tokens to every session and 3,037 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
flow-nexus-platform
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges.
agent-resource-allocator
Agent skill for resource-allocator - invoke with $agent-resource-allocator.
cost-optimization
Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
linkerd-patterns
Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.