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/monoes/monomindWrote 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/monoes/monomind/repo-architect)<a href="https://agentmods.dev/commands/monoes/monomind/repo-architect"><img src="https://agentmods.dev/badge/commands/monoes/monomind/repo-architect/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/monoes/monomind/repo-architect"><img src="https://agentmods.dev/badge/commands/monoes/monomind/repo-architect.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.00028 | $0.02503 |
| Opus 5.5 | $0.00011 | $0.01001 |
| Sonnet 5.5 | $0.00006 | $0.00501 |
| Haiku 4.5 | $0.00003 | $0.00250 |
Grade A, and why
github:repo-architect 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 yesterday.
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 — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Repository Architect
Purpose
Repository structure optimization and multi-repo management with Monomind swarm coordination for scalable project architecture and development workflows.
Capabilities
- Repository structure optimization with best practices
- Multi-repository coordination and synchronization
- Template management for consistent project setup
- Architecture analysis and improvement recommendations
- Cross-repo workflow coordination and management
Tools Available
mcp__github__create_repositorymcp__github__fork_repositorymcp__github__search_repositoriesmcp__github__push_filesmcp__github__create_or_update_filemcp__monomind__*(all swarm coordination tools)TodoWrite,TodoRead,Task,Bash,Read,Write,LS,Glob
Usage Patterns
1. Repository Structure Analysis and Optimization
// Spawn architecture analysis agents
mcp__monomind__agent_spawn { type: "analyst", name: "Structure Analyzer" }
mcp__monomind__agent_spawn { type: "architect", name: "Repository Architect" }
mcp__monomind__agent_spawn { type: "optimizer", name: "Structure Optimizer" }
mcp__monomind__agent_spawn { type: "coordinator", name: "Multi-Repo Coordinator" }
// Analyze current repository structure
LS(".")
// Search for related repositories
mcp__github__search_repositories {
query: "user::owner",
sort: "updated",
order: "desc"
}
// Orchestrate structure optimization
mcp__monomind__task_create {
description: "Analyze and optimize repository structure for scalability and maintainability",
agents: ["analyst", "architect", "optimizer"],
strategy: "parallel"
}
2. Multi-Repository Template Creation
// Create standardized repository template
mcp__github__create_repository {
name: "claude-project-template",
description: "Standardized template for Claude Code projects with monomind integration",
private: false,
autoInit: true
}
// Push template structure
mcp__github__push_files {
owner: ":owner",
repo: "claude-project-template",
branch: "main",
files: [
{
path: ".claude/commands/github/github-modes.md",
content: "[GitHub modes template]"
},
{
path: ".claude/commands/mastermind/help.md",
content: "[Mastermind commands template]"
},
{
path: ".claude/config.json",
content: JSON.stringify({
version: "1.0",
mcp_servers: {
"monomind": {
command: "npx",
args: ["monomind", "mcp", "start"],
stdio: true
}
},
hooks: {
pre_task: "npx monomind hooks pre-task",
post_edit: "npx monomind hooks post-edit",
notification: "npx monomind hooks notify"
}
}, null, 2)
},
{
path: "CLAUDE.md",
content: "[Standardized CLAUDE.md template]"
},
{
path: "package.json",
content: JSON.stringify({
name: "claude-project-template",
version: "1.0.0",
description: "Claude Code project with monomind integration",
engines: { node: ">=20.0.0" },
dependencies: {
"@monomind/cli": "latest"
}
}, null, 2)
},
{
path: "README.md",
content: `# Claude Project Template
## Quick Start
\`\`\`bash
npx monomind init
npm install
npx monomind start --ui
\`\`\`
## Features
- Monomind swarm integration
- GitHub workflow automation
- Advanced coordination capabilities
## Documentation
See CLAUDE.md for complete integration instructions.`
}
],
message: "feat: Create standardized Claude project template with Monomind integration"
}
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.
- yesterday First seen · 372 lines · 28 tokens per session scan A 8eba4116ea11
github:repo-architect is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 28 tokens to every session and 2,503 once invoked, about $0.0001 per session on Opus 5.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-10-26.
Other commands, from other repositories
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
issue-tracker
Intelligent issue management and project coordination with ruv-swarm integration for automated tracking, progress monitoring, and team coordination.
sync-coordinator
Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages.
github-modes
This document describes all GitHub integration modes available in Claude-Flow with ruv-swarm coordination. Each mode is optimized for specific GitHub workflows and includes batch tool integration for maximum efficiency.
pr
Create a GitHub PR from current branch with unpushed commits — discovers templates, analyzes changes, pushes.
bootstrap
Grupo: Framework DT En una frase: Usar El DT como base: promover al raíz y soltar el remoto del template. Cuándo: Arrancar un proyecto nuevo a partir del template. Quién: Cualquier operador del repo.