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 commands/robofinsystems/robosystems/devgit clone --depth 1 https://github.com/RoboFinSystems/robosystemsWhat 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.00010 | $0.00569 |
| Opus 5 | $0.00005 | $0.00284 |
| Sonnet 5 | $0.00002 | $0.00114 |
| Haiku 4.5 | $0.00001 | $0.00057 |
Grade A, and why
dev 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 yesterday.
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 http://localhost:8000/v1/status # API — liveness only How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start the development environment — the full Docker stack under the robosystems profile.
Start
just start
Always use the robosystems profile (the default), never an individual service profile. Add just start robosystems build to rebuild images as part of the start.
Services
The robosystems profile brings up:
| Service | Port | Role |
|---|---|---|
api |
8000 | Main RoboSystems API |
graph-api |
8001 | LadybugDB graph database API |
dagster-webserver |
8002 | Orchestration UI |
dagster-daemon |
— | Schedules and sensors (runs migrations on boot) |
worker |
— | Background task processing |
pg |
5432 | PostgreSQL (platform + extensions databases) |
valkey |
6379 | Cache and queues |
localstack |
4566 | Local AWS emulation |
opensearch |
9200 | Full-text + semantic search |
The frontend apps (robosystems-app, roboledger-app, roboinvestor-app) are on the apps profile and are not started by robosystems. Observability (otel-collector, prometheus, grafana) is on the observability profile.
Confirm what actually came up rather than assuming:
docker compose -f compose.yaml ps
Health checks
curl http://localhost:8000/v1/status # API — liveness only
curl http://localhost:8001/health # Graph API
/v1/status is a liveness probe: it reports healthy whenever the process is up and does not check PostgreSQL, Valkey, or the graph tier. Note the API path is /v1/status — /health and /v1/health do not exist on the main API.
Logs
just logs api # follow one service
just logs dagster-daemon # migrations + schedules land here
just logs-grep worker ERROR # search a service's logs
Run log tailing as a background command rather than backgrounding it with & — a foreground follow will block.
When it doesn't come up
- Code changes not picked up →
just restart - Dependency or Dockerfile changes →
just rebuild - Taxonomy/framework source edits →
just reset-local(tears down, wipes data, rebuilds, reseeds)
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.
- yesterday First seen · 63 lines · 10 tokens per session scan A 21e29c7735eb
dev is a command published in the GitHub repository RoboFinSystems/robosystems (24 stars, last pushed 2d ago), licensed Apache-2.0. It adds 10 tokens to every session and 569 once invoked, about $0.0001 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 commands, from other repositories
fill-event-triage
체결(fill) 이벤트, 특히 매도 체결 후 현금 재배치 판단을 read-only 트리아지로 자동 기동해 dry-run 제안을 남긴다. ROB-755.
crypto-alert-triage
Command "crypto-alert-triage" from mgh3326/auto_trader, covering crypto-alert-triage, 입력, 1. 맥락 복원 (반드시 이 순서), 2. 분석 and 3. dryrun 미리보기 (read-only).
akb-production-review
Review AKB production-governance docs and hooks.
os-meeting
快速创建和管理AI团队会议.
csm-workledger
Show the surviving work-ledger entries across sessions.
scan
Scan AWS account for cost optimization.