Borrowing it
Nothing to install: this file belongs to ddgonzal3/rally. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ddgonzal3/rally/main/CLAUDE.mdgit clone --depth 1 https://github.com/ddgonzal3/rallyWrote 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/instructions/ddgonzal3/rally/claude-md)<a href="https://agentmods.dev/instructions/ddgonzal3/rally/claude-md"><img src="https://agentmods.dev/badge/instructions/ddgonzal3/rally/claude-md.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.1 | $0.02333 | $0.02333 |
| Opus 5 | $0.01167 | $0.01167 |
| Sonnet 5 | $0.00467 | $0.00467 |
| Haiku 4.5 | $0.00233 | $0.00233 |
Grade A, and why
rally CLAUDE.md 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Watcher running** (port 5173 active): Triggers a webview reload via `curl http://localhost:5173/__reload`. The app stays open — no kill, no rebuild. Takes <1 second. How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Rally
What Is This?
Rally is a Tauri v2 macOS app (Rust backend + React frontend) for orchestrating multiple Claude Code sessions, git workflows, and dev processes across repo workspaces.
Build Commands
./scripts/check.sh # Type-check TS + cargo check Rust (fast, no build)
./scripts/build.sh # Full build → .app bundle
./scripts/run.sh # Kill running app → build → relaunch
./scripts/reload.sh # Smart reload: triggers webview reload if watcher running, else falls back to run.sh
./scripts/build-release.sh # Build + .app + .dmg
Never run cargo tauri build without --bundles app unless you want a DMG (slow, opens Finder windows).
IMPORTANT: After Making Changes
Detect the watcher before deciding how to reload. The Vite dev server on port 5173 means cargo tauri dev is running with hot-reload. Use the smart script:
./scripts/reload.sh
This script auto-detects the environment:
- Watcher running (port 5173 active): Triggers a webview reload via
curl http://localhost:5173/__reload. The app stays open — no kill, no rebuild. Takes <1 second. - Watcher NOT running: Falls back to
./scripts/run.sh(kill → rebuild → relaunch).
When to use which
| Change type | Watcher running | Watcher NOT running |
|---|---|---|
| Frontend only (TSX, CSS, HTML) | ./scripts/reload.sh |
./scripts/reload.sh (auto-falls back to run.sh) |
| Rust backend (.rs files) | ./scripts/run.sh (needs Rust recompilation) |
./scripts/run.sh |
Rule of thumb: Use ./scripts/reload.sh for all frontend-only changes. Use ./scripts/run.sh only when Rust code changed.
Architecture
Layers
React Frontend (src/)
├── Components render UI, call Tauri commands via invoke()
├── Zustand store manages workspace + git + pane state
└── xterm.js terminals connect to PTY via Tauri events
Tauri IPC Layer
├── Commands: invoke("command_name", { params }) → Result
└── Events: listen("event-name", callback) for streaming data (PTY output)
Rust Backend (src-tauri/src/)
├── pty_manager.rs — PTY lifecycle (spawn, write, resize, kill)
├── git_ops.rs — Git CLI wrapper
├── commands.rs — Workspace CRUD, file listing
├── config_ops.rs — CLAUDE.md/skills file read/write
└── workspace.rs — Data model + JSON persistence
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.
- 7d ago First seen · 172 lines · 2,333 tokens per session scan A f0b0a8348821
rally CLAUDE.md is an instructions file published in the GitHub repository ddgonzal3/rally (6 stars, last pushed 1mo ago), licensed MIT. It adds 2,333 tokens to every session, about $0.0117 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-31.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.