Skip to content
Back to search

rtmx

MarketplaceWorks with Claude CodeGitHub

First-party RTMX Claude Code plugins — requirements traceability MCP and agent-loop skills.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/rtmx-ai--rtmx/badge.svg)](/listings/rtmx-ai--rtmx)

HTML

<a href="/listings/rtmx-ai--rtmx"><img src="/api/listings/rtmx-ai--rtmx/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

brew install rtmx-ai/tap/rtmx        # macOS / Linux (CLI + broker binary)
scoop install rtmx                    # Windows
go install github.com/rtmx-ai/rtmx/cmd/rtmx@latest

Or download a binary from [releases](https://github.com/rtmx-ai/rtmx/releases). Release archives include both `rtmx` and the `verify` broker daemon.

The packaged verification broker enables automatically on formula/package install and upgrade. If it is still missing, the first `rtmx verify` elevates once. Steady-state `rtmx verify` does not prompt:

rtmx broker status
# manual / fleet: rtmx broker install --prefix="$(brew --prefix rtmx)"
rtmx login
rtmx sync

Self-hosted: `rtmx sync --sync-url sync.example.com/sync/acme/main` (the client adds `wss://`).

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 24 lines
  1. {
  2. "$schema": "https://anthropic.com/claude-code/marketplace.schema.json",
  3. "name": "rtmx",
  4. "description": "First-party RTMX Claude Code plugins — requirements traceability MCP and agent-loop skills.",
  5. "owner": {
  6. "name": "RTMX",
  7. "email": "dev@rtmx.ai"
  8. },
  9. "plugins": [
  10. {
  11. "name": "rtmx",
  12. "source": "./plugins/claude-rtmx",
  13. "description": "RTMX MCP tools (status, backlog, next, claim, verify, …) plus agent-loop and PATH prerequisite skills. Requires rtmx on PATH.",
  14. "version": "2.0.0",
  15. "author": {
  16. "name": "RTMX",
  17. "email": "dev@rtmx.ai"
  18. },
  19. "homepage": "https://github.com/rtmx-ai/rtmx/tree/main/plugins/claude-rtmx",
  20. "category": "development",
  21. "keywords": ["rtmx", "requirements", "mcp", "traceability"]
  22. }
  23. ]
  24. }
README.md · README · 276 lines
  1. # RTMX
  2. **The open source client for [RTMX Sync](https://rtmx.ai/sync) — what comes after Git for humans and agents.**
  3. [![CI](https://github.com/rtmx-ai/rtmx/actions/workflows/ci.yml/badge.svg)](https://github.com/rtmx-ai/rtmx/actions/workflows/ci.yml)
  4. [![Release](https://img.shields.io/github/v/release/rtmx-ai/rtmx)](https://github.com/rtmx-ai/rtmx/releases/latest)
  5. [![Coverage Status](https://coveralls.io/repos/github/rtmx-ai/rtmx/badge.svg?branch=main)](https://coveralls.io/github/rtmx-ai/rtmx?branch=main)
  6. [![Go Report Card](https://goreportcard.com/badge/github.com/rtmx-ai/rtmx)](https://goreportcard.com/report/github.com/rtmx-ai/rtmx)
  7. [![License](https://img.shields.io/badge/License-Apache%202.0-blue.svg)](LICENSE)
  8. ![RTMX workflow](docs/assets/rtmx-workflow.gif)
  9. Git versioned the file. Sync is the room: a live matrix of intent where humans
  10. and agents claim work, converge, and ship. This repo is the Apache 2.0 CLI and
  11. MCP surface — how you enter that room. Local CSV-in-git still works offline;
  12. Sync is how teams stay live.
  13. **[Explore Sync →](https://rtmx.ai/sync)** ·
  14. **[Plans](https://rtmx.ai/pricing)** ·
  15. [Read the backstory](https://rtmx.ai/blog/show-hn-rtmx)
  16. ## Install
  17. ```bash
  18. brew install rtmx-ai/tap/rtmx # macOS / Linux (CLI + broker binary)
  19. scoop install rtmx # Windows
  20. go install github.com/rtmx-ai/rtmx/cmd/rtmx@latest
  21. ```
  22. Or download a binary from [releases](https://github.com/rtmx-ai/rtmx/releases).
  23. Release archives include both `rtmx` and the `verify` broker daemon.
  24. The packaged verification broker enables automatically on formula/package
  25. install and upgrade. If it is still missing, the first `rtmx verify` elevates
  26. once. Steady-state `rtmx verify` does not prompt:
  27. ```bash
  28. rtmx broker status
  29. # manual / fleet: rtmx broker install --prefix="$(brew --prefix rtmx)"
  30. ```
  31. ```bash
  32. rtmx login
  33. rtmx sync
  34. ```
  35. Self-hosted: `rtmx sync --sync-url sync.example.com/sync/acme/main` (the client adds `wss://`).
  36. ## What It Does
  37. | Command | What it does |
  38. |---------|-------------|
  39. | `rtmx sync` | Join a Sync room (hosted or self-managed) |
  40. | `rtmx login` / `checkout` | Managed auth and Team Checkout |
  41. | `rtmx status` | Completion dashboard across all requirements and phases |
  42. | `rtmx next --one` | Pick the highest-priority unblocked requirement |
  43. | `rtmx verify` | Run tests and cross-reference against requirements |
  44. | `rtmx health` | Lint your RTM: orphaned tests, circular deps, stale refs |
  45. | `rtmx backlog` | Prioritized work items with critical path analysis |
  46. | `rtmx mcp-server` | Scientific workflow MCP tools (loop_tick, delivery_check, trades, …) |
  47. 33 commands total. Run `rtmx --help` for the full list.
  48. ![RTMX commands](docs/assets/rtmx-commands.gif)
  49. ## The AI Workflow
  50. ```mermaid
  51. flowchart TD
  52. A["Requirements\n(CSV in git)"] --> B["rtmx next\nPick unblocked requirement"]
  53. B --> C["Agent writes\ncode + tests"]
  54. C --> D{"rtmx verify\nTests pass?"}
  55. D -- yes --> E["Status updates\nautomatically"]
  56. D -- no --> C
  57. E --> F["rtmx status\nTeam sees progress"]
  58. F -.-> B
  59. style A fill:#d1fae5,stroke:#059669,color:#065f46
  60. style B fill:#d1fae5,stroke:#059669,color:#065f46
  61. style C fill:#e5e7eb,stroke:#6b7280,color:#1f2937
  62. style D fill:#fef3c7,stroke:#d97706,color:#92400e
  63. style E fill:#d1fae5,stroke:#059669,color:#065f46
  64. style F fill:#d1fae5,stroke:#059669,color:#065f46
  65. ```
  66. An agent runs `rtmx next --one`, gets a specific requirement, writes code
  67. and tests against the spec, and `rtmx verify` confirms the work is done.
  68. No human triages, assigns, or updates a ticket.
  69. ## Why CSV in Git
  70. ```mermaid
  71. block-beta
  72. columns 1
  73. block:header["database.csv -- Pull Request #42"]
  74. columns 1
  75. end
  76. block:removed["- REQ-AUTH-003, auth, mfa, TOTP-based MFA, ..., missing"]
  77. columns 1
  78. end
  79. block:added["+ REQ-AUTH-003, auth, mfa, TOTP-based MFA, ..., complete, test_totp_flow"]
  80. columns 1
  81. end
  82. block:context[" REQ-AUTH-004, auth, session, Session timeout, ..., partial"]
  83. columns 1
  84. end
  85. style header fill:#6b7280,stroke:#4b5563,color:#ffffff
  86. style removed fill:#dc2626,stroke:#b91c1c,color:#ffffff
  87. style added fill:#16a34a,stroke:#15803d,color:#ffffff
  88. style context fill:#9ca3af,stroke:#6b7280,color:#ffffff
  89. ```
  90. - **Human-readable diffs** in PRs -- one row changed, one requirement done
  91. - **Works everywhere** -- offline, air-gapped, no database, no API
  92. - **AI agents parse it** without an SDK -- it's a file
  93. - **git blame** tells you when and why every requirement changed
  94. - **No vendor lock-in** -- it's your data in your repo
  95. ## MCP Integration
  96. ```mermaid
  97. flowchart LR
  98. subgraph agents["AI Agents"]
  99. direction TB
  100. A1["Claude Code"]
  101. A2["Cursor"]
  102. A3["Custom Agent"]
  103. end
  104. subgraph mcp["rtmx mcp-server"]
  105. direction TB
  106. T1["status"]
  107. T2["backlog"]
  108. T3["next"]
  109. T4["verify"]
  110. T5["health"]
  111. T6["markers"]
  112. T7["deps"]
  113. T1 ~~~ T2 ~~~ T3 ~~~ T4 ~~~ T5 ~~~ T6 ~~~ T7
  114. end
  115. subgraph repo["Git Repository"]
  116. direction TB
  117. DB[".rtmx/database.csv"]
  118. Tests["Test files"]
  119. end
  120. A1 -- "JSON-RPC" --> mcp
  121. A2 -- "JSON-RPC" --> mcp
  122. A3 -- "JSON-RPC" --> mcp
  123. mcp --> DB
  124. mcp --> Tests
  125. style agents fill:#f0fdf4,stroke:#059669,color:#065f46
  126. style mcp fill:#d1fae5,stroke:#10b981,color:#065f46
  127. style repo fill:#f3f4f6,stroke:#6b7280,color:#111827
  128. style A1 fill:#f0fdf4,stroke:#059669,color:#065f46
  129. style A2 fill:#f0fdf4,stroke:#059669,color:#065f46
  130. style A3 fill:#f0fdf4,stroke:#059669,color:#065f46
  131. style DB fill:#d1fae5,stroke:#10b981,color:#065f46
  132. style Tests fill:#d1fae5,stroke:#10b981,color:#065f46
  133. ```
  134. Spine tools (status/backlog/next/claim/…) plus a scientific cycle surface
  135. (`loop_tick`, `decompose`, `hygiene`, `cycles`, `webs`, `context`,
  136. `delivery_check`, `trade_*`). Prefer these over shelling arbitrary CLI.
  137. No generic `run_cli` tool. Mutations require `agent_id`.
  138. Git-native requirements RTM for agents (next, claim, verify) — not another
  139. Jira/Linear MCP. Prefer marketplace / one-click install — the GIF is the
  140. agent calling tools, not a human pasting `mcp.json`.
  141. ([Positioning](docs/POSITIONING.md))
  142. ![RTMX MCP agent session](docs/assets/rtmx-mcp-setup.gif)
  143. **Claude Code** (first-party marketplace):
  144. ```bash
  145. claude plugin marketplace add rtmx-ai/rtmx
  146. claude plugin install rtmx@rtmx
  147. ```
  148. **Cursor** (one-click MCP deeplink):
  149. [Add RTMX in Cursor](https://cursor.com/link/mcp?name=rtmx&config=eyJjb21tYW5kIjoicnRteCIsImFyZ3MiOlsibWNwLXNlcnZlciIsIi0tc3RkaW8iXX0%3D&utm_source=rtmx_readme&utm_medium=referral&utm_campaign=agent_discovery&utm_content=cursor_deeplink)
  150. · [cursor.directory/plugins/rtmx](https://cursor.directory/plugins/rtmx?utm_source=rtmx_readme&utm_medium=referral&utm_campaign=agent_discovery&utm_content=cursor_directory)
  151. **Codex**:
  152. ```bash
  153. codex mcp add rtmx -- rtmx mcp-server --stdio
  154. ```
  155. **One-shot** (marketplace text + offline emit): `rtmx bootstrap agents` —
  156. see [docs/BOOTSTRAP_AGENTS.md](docs/BOOTSTRAP_AGENTS.md).
  157. **Emit** (Claude/Cursor/Codex + long-tail gemini/windsurf/continue/gastown):
  158. `rtmx plugin emit --list` · `rtmx plugin emit --all` — see [docs/LONG_TAIL_EMIT.md](docs/LONG_TAIL_EMIT.md)
  159. Fallback paste (`.cursor/mcp.json` / generic MCP clients):
  160. ```json
  161. {"mcpServers":{"rtmx":{"command":"rtmx","args":["mcp-server","--stdio"]}}}
  162. ```
  163. Details: [docs/CLAUDE_MARKETPLACE.md](docs/CLAUDE_MARKETPLACE.md),
  164. [docs/CURSOR_MARKETPLACE.md](docs/CURSOR_MARKETPLACE.md),
  165. [docs/CODEX_MCP.md](docs/CODEX_MCP.md).
  166. ## Test Verification (2.0.0)
  167. `rtmx verify` auto-detects your test framework. No configuration needed.
  168. Go, Python/pytest, Rust/Cargo, Node.js/npm, Java/Gradle, Java/Maven,
  169. Elixir/Mix, Swift, Dart, Ruby -- 10+ frameworks supported.
  170. **Breaking in 2.0.0:** `COMPLETE` is earned only with a verifying attestation
  171. signature. A results file alone (`rtmx verify --results`) cannot set COMPLETE,
  172. and `rtmx status` counts COMPLETE only when the signature verifies. That is the
  173. verification moat — agents cannot impersonate the verifier. The broker daemon
  174. ships in the same package and enables via install hooks or a one-time elevate
  175. on first `rtmx verify` when missing.
  176. Release notes: [v2.0.0](https://github.com/rtmx-ai/rtmx/releases/tag/v2.0.0) ·
  177. [CHANGELOG.md](CHANGELOG.md)
  178. ## Dogfooding
  179. RTMX manages its own requirements. 219 requirements across 24 phases,
  180. auto-verified in CI on every push. Run `rtmx status` in this repo to see it.
  181. [Read the backstory](https://rtmx.ai/blog/show-hn-rtmx) -- how and why this tool was built.
  182. ## Benchmark Results
  183. Independent testing by [intent-bench](https://github.com/intent-bench/intent-bench)
  184. measures whether providing structured requirements to coding agents improves
  185. implementation effectiveness. Results from N=5 runs per condition using
  186. Claude Sonnet 4:
  187. | Experiment | Complexity | Control | Treatment (RTMX) | Fisher p |
  188. |------------|-----------|---------|-------------------|----------|
  189. | url-shortener | Baseline (10 reqs) | 100% completion | 80% completion | 1.000 |
  190. | task-manager | Standard (13 reqs, depth 5) | 20% completion | 80% completion | 0.206 |
  191. On the baseline task, the intent layer adds overhead without improving
  192. completion. On the standard task with complex dependency chains, completion
  193. increases from 20% to 80% and token variance drops (CV 0.85 to 0.46).
  194. Full data, methodology, and reproduction instructions:
  195. [intent-bench.github.io/intent-bench](https://intent-bench.github.io/intent-bench/)
  196. ## Technical Details
  197. - Single static binary -- Go, `CGO_ENABLED=0`, zero runtime dependencies
  198. - Linux, macOS, Windows -- amd64 and arm64
  199. - 2 external dependencies (Cobra + YAML parser)
  200. - GPG-signed releases with SBOM
  201. - Apache 2.0
  202. ## Contributing
  203. See [CONTRIBUTING.md](CONTRIBUTING.md) for development setup, building,
  204. and testing instructions.
  205. ### Migrating from Python CLI
  206. > **Deprecation Notice:** The Python `rtmx` CLI is deprecated and reached
  207. > end-of-life on 2026-09-25. Run `pip uninstall rtmx` and install the Go
  208. > binary above.
  209. See [docs/MIGRATION.md](docs/MIGRATION.md) for full migration steps.
  210. ## Support
  211. - Discussions: [github.com/rtmx-ai/rtmx/discussions](https://github.com/rtmx-ai/rtmx/discussions)
  212. - Documentation: [rtmx.ai](https://rtmx.ai)
  213. - Issues: [github.com/rtmx-ai/rtmx/issues](https://github.com/rtmx-ai/rtmx/issues)
  214. - Email: dev@rtmx.ai

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.