Borrowing it
Nothing to install: this file belongs to gpt-cmdr/ras-commander. 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/gpt-cmdr/ras-commander/main/.claude/commands/agent-crossrepo.mdgit clone --depth 1 https://github.com/gpt-cmdr/ras-commanderWrote 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/commands/gpt-cmdr/ras-commander/agent-crossrepo)<a href="https://agentmods.dev/commands/gpt-cmdr/ras-commander/agent-crossrepo"><img src="https://agentmods.dev/badge/commands/gpt-cmdr/ras-commander/agent-crossrepo/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/commands/gpt-cmdr/ras-commander/agent-crossrepo"><img src="https://agentmods.dev/badge/commands/gpt-cmdr/ras-commander/agent-crossrepo.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.00000 | $0.00576 |
| Opus 5 | $0.00000 | $0.00288 |
| Sonnet 5 | $0.00000 | $0.00115 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
agent-crossrepo 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are initiating a cross-repository coordination request between ras-commander and hms-commander.
Cross-Repo Coordination Protocol
Key Principles:
- Cross-repo awareness exists ONLY at the AI/documentation layer - NOT in Python code
- All handoffs require explicit HUMAN approval before proceeding
- Communication happens through markdown files in
feature_dev_notes/cross-repo/oragent_tasks/cross-repo/ - Python APIs remain completely independent
Your Task
-
Identify the request type:
- Research/Future Feature → Use
feature_dev_notes/cross-repo/ - Immediate Implementation → Use
agent_tasks/cross-repo/
- Research/Future Feature → Use
-
Create the request file:
- Use naming convention:
{YYYY-MM-DD}_{source}_to_{target}_{topic}.md - Source is current repo (ras-commander)
- Target is sibling repo (hms-commander at
C:\GH\hms-commander)
- Use naming convention:
-
Use the appropriate template:
- Research:
feature_dev_notes/cross-repo/_TEMPLATE_research_request.md - Implementation:
agent_tasks/cross-repo/_TEMPLATE_implementation_request.md
- Research:
-
Fill out the request completely including:
- Clear summary of what is needed
- Background and context
- Relevant files in this repo
- Expected output from sibling repo
- Any constraints or requirements
-
Stop and inform the user:
- Explain what request was created
- Tell them the file path
- Instruct them to review, then open hms-commander and provide the request context
- Remind them that YOU CANNOT directly communicate with the other repo's agent
Sibling Repository Info
| Repository | Path | Purpose |
|---|---|---|
| ras-commander | C:\GH\ras-commander |
HEC-RAS automation (current) |
| hms-commander | C:\GH\hms-commander |
HEC-HMS automation (sibling) |
Example Workflow
1. You create: agent_tasks/cross-repo/2024-12-13_ras_to_hms_dss-export.md
2. You stop and tell user: "Request created. Please review, then open hms-commander."
3. User reviews request
4. User opens hms-commander, provides context
5. hms-commander agent implements, writes response
6. User brings response back here
7. You integrate with user oversight
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.
- 11d ago First seen · 59 lines · 0 tokens per session scan A 35ca25f65304
agent-crossrepo is a command published in the GitHub repository gpt-cmdr/ras-commander (79 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 576 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.