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 parisgroup-ai/imersao-ia-setup --skill railway-debuggit clone --depth 1 https://github.com/parisgroup-ai/imersao-ia-setupWrote 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/parisgroup-ai/imersao-ia-setup/railway-debug)<a href="https://agentmods.dev/skills/parisgroup-ai/imersao-ia-setup/railway-debug"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/railway-debug/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/parisgroup-ai/imersao-ia-setup/railway-debug"><img src="https://agentmods.dev/badge/skills/parisgroup-ai/imersao-ia-setup/railway-debug.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00033 | $0.02704 |
| Opus 5 | $0.00016 | $0.01352 |
| Sonnet 5 | $0.00007 | $0.00541 |
| Haiku 4.5 | $0.00003 | $0.00270 |
Grade A, and why
railway-debug 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 11d 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 — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Railway Debug
Analyze Railway production logs, identify errors, and guide the fix for deploy and production issues.
Persistent memory: Check project memory for Railway-specific notes before any action.
Debug Workflow
0. CHECK MEMORY
- Read project memory for Railway notes
- Check known pitfalls and tested commands
1. COLLECT CONTEXT
- railway status (project and environment)
- Identify which service has the problem
2. ANALYZE LOGS
- Runtime logs (production errors)
- Build logs (deploy errors)
- Filter by error level
3. ACCESS PRODUCTION DB (if needed)
- Use public URL (switchyard.proxy.rlwy.net)
- NEVER use internal hostname (.railway.internal)
4. IDENTIFY ROOT CAUSE
- Categorize error type
- Correlate with local code
5. PROPOSE AND APPLY FIX
- Suggest specific fix
- Apply fix in code
- Validate locally before deploy
6. VERIFY FIX
- Re-deploy
- Confirm clean logs
7. UPDATE MEMORY
- Save lessons learned
Railway CLI Commands (Tested and Working)
Commands that WORK
# General status (shows project, environment, current service)
railway status
# View variables for a specific service
railway variables --service <service-name>
# Execute command with Railway env vars injected
railway run -- node -e "console.log(process.env.DATABASE_URL ? 'ok' : 'no')"
# Runtime logs
railway logs -n 100 --service <service-name>
# Build logs
railway logs -n 200 --service <service-name> --build
# Redeploy
railway redeploy --service <service-name> --yes
# Variables as JSON (avoids table truncation)
railway variables --service <service-name> --json
Commands that DO NOT WORK (pitfalls)
# DOES NOT WORK: service list (does not exist)
railway service list # "Service not found"
# DOES NOT WORK: railway run with psql (internal hostname)
railway run -- psql "$DATABASE_URL" -c "SELECT 1"
# Fails because DATABASE_URL = postgres.railway.internal (only resolves inside Railway)
# DOES NOT WORK: interactive prompts
railway service # Requires TTY to select service
# DOES NOT WORK: railway link --service (requires TTY)
railway link --service <name> # Can't be scripted
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.
- 11d ago First seen · 410 lines · 33 tokens per session scan A 436d7ad6cf21
railway-debug is a skill published in the GitHub repository parisgroup-ai/imersao-ia-setup (1 stars, last pushed 29d ago), licensed MIT. It adds 33 tokens to every session and 2,704 once invoked, about $0.0002 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-31.
Other skills, from other repositories
architecture-optimization
Guided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer …
remove-technical-debt
Guided journey from a large aged codebase everyone fears to touch to one that is safe to change, legible, bounded, and resilient - paid down in place without a rewrite. Orchestrates eight skills phase by phase - working-with-legacy-code, refactoring-patterns, clean-code, software-design-philosophy, clean-architecture…
release-it
Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or…
cloudflare-workers-dev-experience
Cloudflare Workers local development with Wrangler, Miniflare, hot reload, debugging. Use for project setup, wrangler.jsonc configuration, or encountering local dev, HMR, binding simulation errors.
cloudflare-workers-performance
Cloudflare Workers performance optimization with CPU, memory, caching, bundle size. Use for slow workers, high latency, cold starts, or encountering CPU limits, memory issues, timeout errors.
orca-k8s-connector-troubleshoot
Diagnoses Kubernetes Connector (K8s Tunnel Client / Helm chart orca-tunnel) install and connectivity failures from raw customer input — error text, helm status, kubectl describe, or pod logs — and walks through step-by-step remediation. Use when a user reports the K8s Connector won't install, won't connect, keeps…