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 artivilla/agents-config --skill central-stationgit clone --depth 1 https://github.com/artivilla/agents-configWrote 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/artivilla/agents-config/central-station)<a href="https://agentmods.dev/skills/artivilla/agents-config/central-station"><img src="https://agentmods.dev/badge/skills/artivilla/agents-config/central-station/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/artivilla/agents-config/central-station"><img src="https://agentmods.dev/badge/skills/artivilla/agents-config/central-station.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.00069 | $0.01868 |
| Opus 5 | $0.00034 | $0.00934 |
| Sonnet 5 | $0.00014 | $0.00374 |
| Haiku 4.5 | $0.00007 | $0.00187 |
Grade B, and why
central-station scanned grade B with 2 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 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -s 'https://station-server.railway.com/gql' -H 'content-type: application/json' -d '{"query": "{ topics { slug } }"}' Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Bash(curl:*), Bash(jq:*) How it starts
The opening of the file, as written. The whole thing — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Central Station
Search and browse Railway's Central Station - the community support platform for threads, discussions, and documentation.
API Endpoints
| Endpoint | URL |
|---|---|
| GraphQL | https://station-server.railway.com/gql |
| Thread Markdown | https://station-server.railway.com/api/threads/:slug |
| LLM Data Export | https://station-server.railway.com/api/llms-station |
| Frontend | https://station.railway.com |
When to Use
- User wants to search Central Station threads or docs
- User asks about community discussions or support questions
- User wants to find threads about a specific topic (deployments, databases, etc.)
- User asks "what are people asking about X"
- User wants to see recent threads or questions
- User mentions Central Station, community threads, or support discussions
- User wants to find existing solutions before creating a new thread
When NOT to Use
- User wants Railway product documentation - use
railway-docsskill - User wants to check their project status - use
statusskill - User wants to manage their Railway project - use appropriate skill (deploy, environment, etc.)
Docs Search
For official Railway documentation, use the railway-docs skill which fetches from https://docs.railway.com/api/llms-docs.md.
Central Station's unifiedSearch can identify document types but has limited field access:
curl -s 'https://station-server.railway.com/gql' \
-H 'content-type: application/json' \
--data-raw '{"query":"{ unifiedSearch(input: { query: \"volumes\", limit: 10 }) { results { document { __typename } } } }"}'
Document types returned: EsThreadItem (threads) and DocSearchResult (docs).
Note: For searching thread content, use the LLM Data Export endpoint instead (see below) which provides full thread data.
Quick Actions
Get Recent Threads
Fetch recent threads, optionally filtered by topic:
curl -s 'https://station-server.railway.com/gql' \
-H 'content-type: application/json' \
-d '{"query": "{ threads(first: 10, sort: recent_activity) { edges { node { slug subject status topic { slug displayName } upvoteCount createdAt } } } }"}'
What ships with it
4 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 · 227 lines · 69 tokens per session scan B bdd9f1f93fd5
central-station is a skill published in the GitHub repository artivilla/agents-config (0 stars, last pushed 3mo ago), licensed MIT. It adds 69 tokens to every session and 1,868 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
workers-best-practices
Cloudflare Workers best practices for production applications. Use when writing, reviewing, or configuring Workers.
find-journalists
Build, refine, dedupe, and enrich small fit-checked journalist lists for newsjack campaigns. Uses the newsjack CLI (preferred) or the medialyst MCP for news search and journalist enrichment, and falls back to a best-effort local mode with no verified contacts; the agent owns how returned data is organized.
story-origin-check
Recover the first public timestamp and canonical major coverage for a newsjacking signal, then decide whether newer coverage is the same story, a different story, or a materially new development.
relevance-coarse-filter
Cheap, high-recall first-pass filter that removes obvious junk from a detector candidate pool before expensive story-origin research and PR judgment. Decides keep, monitoronly, or reject — never ranks, writes angles, verifies dates, or decides whether to pitch.
annotating-task-lineage
Annotate Airflow tasks with data lineage using inlets and outlets. Use when the user wants to add lineage metadata to tasks, specify input/output datasets, or enable lineage tracking for operators without built-in OpenLineage extraction.
ai-visibility-writing
Audit, question, suggest, or fact-preservingly revise a press release, blog post, contributed article, or expert explainer so AI answer systems can more easily retrieve, understand, quote, and cite its useful information. Use when someone asks for AI visibility, AI search, answer-engine, AEO, GEO, AI Overview, or…