agent-repo-architect

agent-repo-architect is a skill for Claude Code from proffesor-for-testing/agentic-qe. It costs 21 tokens per session (3,070 once invoked), scanned A, a copy of agent-repo-architect, MIT.

A repository-architecture skill for organizing project structure and managing multiple code repositories with help from coordinated AI agents.

In plain words
What is it for?
Use it to analyze repository layouts, plan architecture changes, manage repositories, and update structure documentation.
Why use it?
It helps identify structural problems and keep large or split-up codebases easier to manage.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions CLAUDE.md; names the TodoWrite tool; mentions Claude Code.

Part of the claude-flow plugin — 123 skills, 8 commands, 9 agents shipped together

Good fit Use it to analyze repository layouts, plan architecture changes, manage repositories, and update structure documentation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/proffesor-for-testing/agentic-qe/agent-repo-architect
Install

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.

Any agent
npx skills add proffesor-for-testing/agentic-qe --skill agent-repo-architect
Clone the repo
git clone --depth 1 https://github.com/proffesor-for-testing/agentic-qe

Made for: Claude Code.

Or install claude-flow, the plugin that ships this one along with the rest of its 123 skills, 8 commands, 9 agents.

Wrote 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.

agentmods badge for agent-repo-architect

README.md
[![agentmods](https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/agent-repo-architect/github.svg)](https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/agent-repo-architect)
Your own site
<a href="https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/agent-repo-architect"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/agent-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.

agentmods 80×15 button for agent-repo-architect

Your own site · 80×15
<a href="https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/agent-repo-architect"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/agent-repo-architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,070 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.03070
Opus 5.5 $0.00008 $0.01228
Sonnet 5.5 $0.00004 $0.00614
Haiku 4.5 $0.00002 $0.00307

Measured 1mo ago against content hash b4058daa7b95, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

agent-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 1mo 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.

Origin

This is a copy

100% identical to agent-repo-architect — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/ruflo/.agents/skills/agent-repo-architect/SKILL.md · 403 lines

How it starts

The opening of the file, as written. The whole thing — 403 lines — stays where its author put it; the contents beside it link to each section on GitHub.


name: repo-architect description: Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows type: architecture color: "#9B59B6" tools:

  • Bash
  • Read
  • Write
  • Edit
  • LS
  • Glob
  • TodoWrite
  • TodoRead
  • Task
  • WebFetch
  • mcp__github__create_repository
  • mcp__github__fork_repository
  • mcp__github__search_repositories
  • mcp__github__push_files
  • mcp__github__create_or_update_file
  • mcp__claude-flow__swarm_init
  • mcp__claude-flow__agent_spawn
  • mcp__claude-flow__task_orchestrate
  • mcp__claude-flow__memory_usage hooks: pre_task: | echo "🏗️ Initializing repository architecture analysis..." npx ruv-swarm hook pre-task --mode repo-architect --analyze-structure post_edit: | echo "📐 Validating architecture changes and updating structure documentation..." npx ruv-swarm hook post-edit --mode repo-architect --validate-structure post_task: | echo "🏛️ Architecture task completed. Generating structure recommendations..." npx ruv-swarm hook post-task --mode repo-architect --generate-recommendations notification: | echo "📋 Notifying stakeholders of architecture improvements..." npx ruv-swarm hook notification --mode repo-architect

GitHub Repository Architect

Purpose

Repository structure optimization and multi-repo management with ruv-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

Usage Patterns

1. Repository Structure Analysis and Optimization

// Initialize architecture analysis swarm
mcp__claude-flow__swarm_init { topology: "mesh", maxAgents: 4 }
mcp__claude-flow__agent_spawn { type: "analyst", name: "Structure Analyzer" }
mcp__claude-flow__agent_spawn { type: "architect", name: "Repository Architect" }
mcp__claude-flow__agent_spawn { type: "optimizer", name: "Structure Optimizer" }
mcp__claude-flow__agent_spawn { type: "coordinator", name: "Multi-Repo Coordinator" }

// Analyze current repository structure
LS("$workspaces$ruv-FANN$claude-code-flow$claude-code-flow")
LS("$workspaces$ruv-FANN$ruv-swarm$npm")

// Search for related repositories
mcp__github__search_repositories {
  query: "user:ruvnet claude",
  sort: "updated",
  order: "desc"
}

// Orchestrate structure optimization
mcp__claude-flow__task_orchestrate {
  task: "Analyze and optimize repository structure for scalability and maintainability",
  strategy: "adaptive",
  priority: "medium"
}

Read the full file on GitHub · 403 lines

Changes

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.

  1. 1mo ago First seen · 403 lines · 21 tokens per session scan A b4058daa7b95

Subscribe to this mod's changes

agent-repo-architect is a skill published in the GitHub repository proffesor-for-testing/agentic-qe (515 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 3,070 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to agent-repo-architect, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

component-fixtures

Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.

microsoft/vscode · 53 tokens