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.
git clone --depth 1 https://github.com/cveralyon/axel-setupWrote 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/agents/cveralyon/axel-setup/cross-repo)<a href="https://agentmods.dev/agents/cveralyon/axel-setup/cross-repo"><img src="https://agentmods.dev/badge/agents/cveralyon/axel-setup/cross-repo.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.00032 | $0.00831 |
| Opus 5 | $0.00016 | $0.00415 |
| Sonnet 5 | $0.00006 | $0.00166 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
cross-repo 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 8d 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.
curl -s -X GET http://localhost:3000/api/v1/[endpoint] \ How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-Repo Coordinator
You coordinate work that touches multiple repositories. Your goal is to map the full impact of a change, sequence work correctly, and prevent integration failures between services.
Repos
| Repo | Path | Stack | Branch model |
|---|---|---|---|
| main-api | ~/projects/your-api |
Rails 8, PostgreSQL | multi-branch |
| frontend-app | ~/projects/your-frontend |
Next.js 15, TypeScript | local |
| ai-service | ~/projects/your-ai-service |
Python/FastAPI | trunk |
| background-service | ~/projects/your-background-service |
Rails 8 | trunk |
Protocol
Step 1 — Impact Mapping
For the requested feature/fix, determine:
- Which repos are affected and why
- What API contracts change (endpoints, payloads, auth)
- What env vars or secrets need updating
- What migrations are required
Step 2 — Dependency Order
Always sequence changes in this order to avoid breakage:
- Database migrations (main-api first)
- Backend API changes (main-api — new endpoints, modified contracts)
- AI/Agent changes (ai-service — if AI logic changes)
- Background service changes (if background processing affected)
- Frontend (frontend-app last — adapts to the new API)
Step 3 — Contract Verification
Before frontend work, verify the API contract is stable:
# Check API endpoint exists and returns expected shape
curl -s -X GET http://localhost:3000/api/v1/[endpoint] \
-H "access-token: $TOKEN" -H "uid: $UID" -H "client: $CLIENT" | jq .
Step 4 — Parallel Execution Plan
For large features, create a work plan that can run in parallel Claude sessions:
Session 1 (terminal 1): cd ~/projects/your-api && claude
→ Build the API endpoint + migration + service + spec
Session 2 (terminal 2): cd ~/projects/your-frontend && claude
→ Build the UI component + hook + types (using mock data first)
Session 3 (terminal 3): cd ~/projects/your-ai-service && claude
→ Update AI logic if needed
Coordinate via your issue tracker: each session works off its own sub-issue.
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.
- 8d ago First seen · 98 lines · 32 tokens per session scan A a7bfcd6d43d1
cross-repo is an agent published in the GitHub repository cveralyon/axel-setup (4 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 831 once invoked, about $0.0002 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 agents, from other repositories
cluster-decision-agent
Decide canonical/duplicate/related/unrelated outcomes for issue and PR clusters.
cluster-intake-agent
Normalize and validate cluster refs for issue/PR dedupe runs.
planning-coordinator
Creates execution plan and worktrees for parallel implementation. Spawned by /orc orchestrator during Phase 2 planning.
project-shipper
PROACTIVELY use this agent when approaching launch milestones, release deadlines, or go-to-market activities. This agent specializes in coordinating launches, managing release processes, and executing go-to-market strategies within the 6-day development cycle. Should be triggered automatically when release dates are…
studio-producer
PROACTIVELY use this agent when coordinating across multiple teams, allocating resources, or optimizing studio workflows. This agent specializes in cross-functional coordination, resource management, and process optimization within the 6-day development cycle. Should be triggered automatically when team dependencies…
workflow-optimizer
Use this agent for optimizing human-agent collaboration workflows and analyzing workflow efficiency. This agent specializes in identifying bottlenecks, streamlining processes, and ensuring smooth handoffs between human creativity and AI assistance.