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/commands/cveralyon/axel-setup/multi-repo-feature)<a href="https://agentmods.dev/commands/cveralyon/axel-setup/multi-repo-feature"><img src="https://agentmods.dev/badge/commands/cveralyon/axel-setup/multi-repo-feature/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/cveralyon/axel-setup/multi-repo-feature"><img src="https://agentmods.dev/badge/commands/cveralyon/axel-setup/multi-repo-feature.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.00518 |
| Opus 5 | $0.00000 | $0.00259 |
| Sonnet 5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
multi-repo-feature 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 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.
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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Repo Feature Coordinator
Coordinate a feature that spans multiple repos. Creates a parallel work plan and sequences changes correctly.
Input
Describe the feature or provide a Linear issue ID. Example:
- "Implementar filtro de candidatos por idioma en API y frontend"
- "MAI-123"
Steps
1. Understand the Feature
If a Linear issue ID is provided, fetch it with the Linear MCP tool to get full context, acceptance criteria, and comments.
2. Impact Analysis
For each repo, determine:
- main-api: new/modified endpoints, migrations, services, background jobs
- frontend-app: new/modified pages, components, hooks, API calls, i18n keys
- ai-service: new/modified agents, prompts, contracts (only if AI logic involved)
- background-service: new/modified background processing (only if affected)
3. API Contract First
If API changes are needed, define the contract before writing any code:
Endpoint: METHOD /api/v1/[resource]
Auth: required / public
Request: { field: type }
Response: { data: { field: type } }
Errors: 422 { errors: [...] }
4. Sequenced Work Plan
Output a sequenced plan respecting the dependency order:
- Migrations (API first)
- Backend services + endpoints
- AI/Agent logic (if needed)
- Frontend components + hooks
5. Parallel Session Setup
For large features (3+ files per repo), suggest opening parallel Claude sessions:
# Terminal 1 — API
cd ~/projects/your-api && cl
# Prompt: "Implement [backend part] following the contract: [contract]"
# Terminal 2 — Frontend (can start with mock data)
cd ~/projects/your-frontend && cl
# Prompt: "Implement [frontend part] against this API contract: [contract]"
6. Integration Checklist
Generate a checklist for verifying the full feature works end-to-end:
- Migration applied (
RAILS_ENV=development rails db:migrate) - API endpoint returns correct shape
- Frontend displays data correctly
- i18n keys added in all locales (en, es, ca, fr)
- Specs written and passing
- No TypeScript errors (
pnpm typecheck) - Linear issue updated with implementation notes
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 · 61 lines · 0 tokens per session scan A c262213ecab8
multi-repo-feature is a command published in the GitHub repository cveralyon/axel-setup (4 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 518 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-31.
Other commands, from other repositories
commit-push-pr
An automated Git workflow that checks a project, synchronizes documentation, commits changes, and can create or merge a GitHub pull request. A pull request is a request for teammates to review and add changes to a shared codebase.
auto
An automated coding workflow runs a software task from planning through code changes, checks, and a pull request. A pull request is a proposed change for review before it is merged into the main codebase.
sync
A command that pulls the latest code from the main Git branch and updates the project's key planning and instruction documents to match it.
pull
A quick command that downloads the latest commits from the main Git branch into the current project.
worktree-cleanup
A command for removing a Git worktree, which is a separate working folder linked to the same repository, after its pull request is merged.
quick-commit
A quick Git command for committing and pushing a small code change. Git is the tool that records code versions and sends them to a shared repository.