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.
npx skills add ayushcodes10/echo-mem --skill github-multi-repogit clone --depth 1 https://github.com/ayushcodes10/echo-memWrote 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/skills/ayushcodes10/echo-mem/github-multi-repo)<a href="https://agentmods.dev/skills/ayushcodes10/echo-mem/github-multi-repo"><img src="https://agentmods.dev/badge/skills/ayushcodes10/echo-mem/github-multi-repo/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/skills/ayushcodes10/echo-mem/github-multi-repo"><img src="https://agentmods.dev/badge/skills/ayushcodes10/echo-mem/github-multi-repo.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.00022 | $0.05718 |
| Opus 5 | $0.00011 | $0.02859 |
| Sonnet 5 | $0.00004 | $0.01144 |
| Haiku 4.5 | $0.00002 | $0.00572 |
Grade A, and why
github-multi-repo 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 today.
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 — 863 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Multi-Repository Coordination Skill
Overview
Advanced multi-repository coordination system that combines swarm intelligence, package synchronization, and repository architecture optimization. This skill enables organization-wide automation, cross-project collaboration, and scalable repository management.
Core Capabilities
🔄 Multi-Repository Swarm Coordination
Cross-repository AI swarm orchestration for distributed development workflows.
📦 Package Synchronization
Intelligent dependency resolution and version alignment across multiple packages.
🏗️ Repository Architecture
Structure optimization and template management for scalable projects.
🔗 Integration Management
Cross-package integration testing and deployment coordination.
Quick Start
Initialize Multi-Repo Coordination
# Basic swarm initialization
npx Codex-flow skill run github-multi-repo init \
--repos "org/frontend,org/backend,org/shared" \
--topology hierarchical
# Advanced initialization with synchronization
npx Codex-flow skill run github-multi-repo init \
--repos "org/frontend,org/backend,org/shared" \
--topology mesh \
--shared-memory \
--sync-strategy eventual
Synchronize Packages
# Synchronize package versions and dependencies
npx Codex-flow skill run github-multi-repo sync \
--packages "Codex-flow,ruv-swarm" \
--align-versions \
--update-docs
Optimize Architecture
# Analyze and optimize repository structure
npx Codex-flow skill run github-multi-repo optimize \
--analyze-structure \
--suggest-improvements \
--create-templates
Features
1. Cross-Repository Swarm Orchestration
Repository Discovery
// Auto-discover related repositories with gh CLI
const REPOS = Bash(`gh repo list my-organization --limit 100 \
--json name,description,languages,topics \
--jq '.[] | select(.languages | keys | contains(["TypeScript"]))'`)
// Analyze repository dependencies
const DEPS = Bash(`gh repo list my-organization --json name | \
jq -r '.[].name' | while read -r repo; do
gh api repos/my-organization/$repo/contents/package.json \
--jq '.content' 2>/dev/null | base64 -d | jq '{name, dependencies}'
done | jq -s '.'`)
// Initialize swarm with discovered repositories
mcp__claude-flow__swarm_init({
topology: "hierarchical",
maxAgents: 8,
metadata: { repos: REPOS, dependencies: DEPS }
})
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.
- today Changed 6aea9f0ea39b
- 2d ago First seen · 863 lines · 22 tokens per session scan A 4bffcdde56dd
github-multi-repo is a skill published in the GitHub repository ayushcodes10/echo-mem (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 22 tokens to every session and 5,718 once invoked, about $0.0001 per session on Opus 5. 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-09-10.
Other skills, from other repositories
github-ops
GitHub CLI for issues, PRs, code search, CI logs, releases, and API queries. Requires gh CLI and auth.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-notification-triage
Triage GitHub notifications and issue/PR queues.
meta-feedback
A feedback reporter that collects bug reports and feature requests, then formats them as GitHub Issues. GitHub Issues are shared records used by development teams to track work and problems.