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/robium-ai/robium/architectnpx skills add robium-ai/robium --skill architectgit clone --depth 1 https://github.com/robium-ai/robiumWrote 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/robium-ai/robium/architect)<a href="https://agentmods.dev/skills/robium-ai/robium/architect"><img src="https://agentmods.dev/badge/skills/robium-ai/robium/architect.svg" alt="Measured on agentmods" 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 | $0.00193 | $0.02678 |
| Opus 5 | $0.00097 | $0.01339 |
| Sonnet 5 | $0.00039 | $0.00536 |
| Haiku 4.5 | $0.00019 | $0.00268 |
Grade A, and why
architect 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 3d 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.
This is a copy
98% identical to architect — 16 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
architect
The entry point for a new Robium application. It combines a lean design conversation with robotics stack selection, chooses the cheapest meaningful proof, records decisions without freezing provisional assumptions, and routes implementation to the skills that own each layer.
When to use this skill
- Starting a new robotics application from a rough idea.
- Choosing or reconsidering the stack, simulator, embodiment, environment, data path, visualization, or compute target.
- Decomposing a multi-subsystem robotics idea into a first buildable slice.
- Writing a durable decision record for a new app or genuine re-architecture.
- Skip architect for a bounded change in an existing flow. Read the affected code and use the matching tool skill directly.
Key directives
- Delegation posture: route + embed decision logic. Architect owns the product/stack choices and routing. Tool mechanics stay in the skill that owns them.
- Brainstorm only where a real decision exists. Inspect the repository and
robium-appsregistry first. Ask only questions whose answers materially change the first slice. For a genuine choice, offer 2–3 approaches with trade-offs and recommend one. Never announce a process classification. - One direction gate, then build. A new app or material architecture gets one rough direction approval. After that, proceed through implementation and verification; pause only for a material pivot, scope expansion, paid or publishing action, deployment, or safety concern.
- Prove the riskiest assumption cheaply. Before polishing infrastructure or scaling compute, run the smallest probe that can disprove the stack and deliver the first user-visible working slice. Label provisional choices and update them when evidence changes.
- Use a decision record, not a contract. Create or update
docs/architecture-brief.mdfor a new application or genuine re-architecture. It records validated decisions, provisional assumptions, risks, and authorized pivots. Bounded feature/fix work does not require a new brief or approval cycle.
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.
- 3d ago First seen · 205 lines · 193 tokens per session scan A 6707c7be476b
architect is a skill published in the GitHub repository robium-ai/robium (9 stars, last pushed 5d ago), licensed MIT. It adds 193 tokens to every session and 2,678 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to architect, differing in 16 lines, and is treated as a copy.
Other skills, from other repositories
ros2-microros
Skill "ros2-microros" from Leehyunbin0131/claude-ros2-skills, covering micro-ros instructions (ubuntu 24.04 lts & ros 2 jazzy), 1. architecture, 2. documentation entry points, 3. key concepts & patterns and a. embedded client node setup (rclc in c).
ros2-troubleshooting
Diagnose ROS 2 Jazzy faults that reading the code cannot settle: QoS mismatch, sensor-mount and frame errors (REP 103/105), and odometry calibrated against CAD instead of the floor. Ships four runnable pass/fail checks.
gazebo-mcp
Gazebo / gz-sim worlds, models, poses (mock + live bridge). CLI gazebo-mcp + MCP stdio serve. Use when the user mentions gazebo-mcp, /gazebo-mcp, or related domain work. One-command Grok install from GitHub.
attach-end-effector
Mount an end-effector (parallel-jaw gripper, dexterous hand, suction tool, etc.) on a robot arm by attaching its MJCF to the arm's attachmentsite via MuJoCo's MjSpec API. Use when combining an arm MJCF and an end-effector MJCF into a single combined model. Handles known gotchas the underlying script doesn't: mesh…
urdf-to-mjcf
Use when bringing a URDF robot, hand, or CAD-generated model into MuJoCo MJCF and no hand-tuned upstream MJCF exists.
mjcf-to-urdf
Convert an MJCF (MuJoCo's XML format) to URDF for downstream consumers that don't speak MJCF (RViz, pinocchio, ROS-based motion planning, etc.). The conversion is lossy — constraints, position actuators, contact excludes, and keyframes are all dropped. Use this skill ONLY when a URDF-only consumer needs the kinematic…