Senior Architect
alirezarezvani/claude-skills
This skill should be used when the user asks to "design system architecture", "evaluate microservices vs monolith", "create architecture diagrams", "analyze dependencies", "choose a database", "plan…
Architecture specialist for software/system design, module and service boundaries, tradeoff analysis, and stakeholder synthesis.
Install Oma Architecture
$ npx skills add first-fluke/oh-my-agent --skill oma-architecture -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install first-fluke/oh-my-agent oma-architecture --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/benchmarks/runs/oma/.agents/skills/oma-architecture .claude/skills/oma-architecture && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "oma-architecture" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/benchmarks/runs/oma/.agents/skills/oma-architecture into .claude/skills/oma-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-architecture", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/first-fluke/oh-my-agent/tree/main/benchmarks/runs/oma/.agents/skills/oma-architectureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add first-fluke/oh-my-agent --skill oma-architecture -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install first-fluke/oh-my-agent oma-architecture --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/benchmarks/runs/oma/.agents/skills/oma-architecture .agents/skills/oma-architecture && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "oma-architecture" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/benchmarks/runs/oma/.agents/skills/oma-architecture into .agents/skills/oma-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-architecture", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add first-fluke/oh-my-agent --skill oma-architecture -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install first-fluke/oh-my-agent oma-architecture --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/benchmarks/runs/oma/.agents/skills/oma-architecture .cursor/skills/oma-architecture && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "oma-architecture" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/benchmarks/runs/oma/.agents/skills/oma-architecture into .cursor/skills/oma-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-architecture", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/first-fluke/oh-my-agent.git --path benchmarks/runs/oma/.agents/skills/oma-architecture--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add first-fluke/oh-my-agent --skill oma-architecture -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install first-fluke/oh-my-agent oma-architecture --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/benchmarks/runs/oma/.agents/skills/oma-architecture .gemini/skills/oma-architecture && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "oma-architecture" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/benchmarks/runs/oma/.agents/skills/oma-architecture into .gemini/skills/oma-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-architecture", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install first-fluke/oh-my-agent oma-architectureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add first-fluke/oh-my-agent --skill oma-architecture -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .github/skills && cp -r skills-src/benchmarks/runs/oma/.agents/skills/oma-architecture .github/skills/oma-architecture && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "oma-architecture" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/benchmarks/runs/oma/.agents/skills/oma-architecture into .github/skills/oma-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-architecture", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add first-fluke/oh-my-agent --skill oma-architecture -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install first-fluke/oh-my-agent oma-architecture --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/first-fluke/oh-my-agent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/benchmarks/runs/oma/.agents/skills/oma-architecture .opencode/skills/oma-architecture && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "oma-architecture" agent skill from https://github.com/first-fluke/oh-my-agent/tree/main/benchmarks/runs/oma/.agents/skills/oma-architecture into .opencode/skills/oma-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oma-architecture", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
oma-architecture- GitHub stars
- 1.3k
- Token cost
- ~2.1k tokens
- SKILL.md length
- 840 words
- Files
- 7
- Skills in repo
- 57
- Repo updated
- First seen
- Licence
- MIT
At a glance
Architecture specialist for software/system design, module and service boundaries, tradeoff analysis, and stakeholder synthesis.
- Works in 3 steps: Identify the architecture problem,… → Gather existing constraints, source… → Select the lightest sufficient method.
- Tasks that involve Architecture decision records
- SKILL.md covers Scheduling, Structural Flow, Logical Operations and References
- Calls rg
What it does
Oma Architecture is an agent skill from first-fluke/oh-my-agent. Architecture specialist for software/system design, module and service boundaries, tradeoff analysis, and stakeholder synthesis. Uses context-aware methods such as diagnostic routing, design-twice comparison, ATAM-style risk analysis, CBAM-style prioritization, and ADR-style decision records.
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files (for example `resources/checklist.md`, `resources/examples.md` and `resources/execution-protocol.md`).
It sits in Development, covering Architecture decision records, Prioritization frameworks and Microservices. The repository describes itself as: Mechanical verification for AI coding agents — skills pack or full harness (stop-hook gates, artifact checks, independent judges). The licence is MIT.
When your agent uses it
- Tasks that involve Architecture decision records
- Tasks that involve Prioritization frameworks
- Tasks that involve Microservices
Example prompts
- “/oma-architecture”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Identify the architecture problem, decision, or pain signal.
- Gather existing constraints, source evidence, and stakeholder context.
- Select the lightest sufficient method.
What it can do on your machine
Read from SKILL.md and the folder at commit b364119. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
rg
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Oma Architecture loads about 2.1k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 840 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from first-fluke/oh-my-agent at commit b364119, republished under its MIT licence (© first-fluke). 840 words, ~2,060 tokens.
Download SKILL.mdSave it as
.claude/skills/oma-architecture/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.- name
- oma-architecture
- description
- Architecture specialist for software/system design, module and service boundaries, tradeoff analysis, and stakeholder synthesis. Uses context-aware methods such as diagnostic routing, design-twice comparison, ATAM-style risk analysis, CBAM-style prioritization, and ADR-style decision records.
Architecture Agent - Software Architecture Specialist
Scheduling
Goal
Analyze, compare, and document software architecture decisions with explicit tradeoffs, risks, stakeholder concerns, and validation steps.
Intent signature
- User asks for architecture, system design, module/service boundaries, ADRs, or design tradeoffs.
- User needs a decision method such as diagnostic routing, design-twice comparison, ATAM-style risk analysis, or CBAM-style prioritization.
- User reports architecture pain such as change amplification, hidden dependencies, unclear ownership, or awkward APIs.
When to use
- Choosing or reviewing system architecture
- Defining module, service, or ownership boundaries
- Comparing architectural options with explicit tradeoffs
- Investigating architectural pain: change amplification, hidden dependencies, awkward APIs
- Prioritizing architecture investments or refactors
- Writing architecture recommendations or ADRs
When NOT to use
- Visual design, design systems, branding, or landing pages -> use oma-design
- Feature planning and task decomposition -> use oma-pm
- Infrastructure provisioning or Terraform implementation -> use oma-tf-infra
- Bug diagnosis and code fixes -> use oma-debug
- Security/performance/accessibility review -> use oma-qa
Expected inputs
- Architecture question, pain point, or decision context
- Existing codebase, diagrams, docs, constraints, or stakeholder concerns
- Quality attributes such as scalability, reliability, security, operability, cost, and delivery speed
- Optional target artifact type such as recommendation, option comparison, or ADR
Expected outputs
- Architecture diagnosis, recommendation, comparison, prioritization, or ADR
- Assumptions, tradeoffs, risks, and validation steps
- Saved architecture artifacts under
.agents/results/architecture/when producing durable outputs
Dependencies
resources/execution-protocol.mdfor workflowresources/methodology-selection.mdfor method choiceresources/stakeholder-synthesis.mdwhen cross-cutting stakeholder consultation is justifiedresources/output-templates.mdfor final artifact shapes
Control-flow features
- Branches by request clarity, decision materiality, risk level, and need for stakeholder consultation
- May compare multiple options before recommending one
- Produces source-grounded docs rather than directly changing implementation
Structural Flow
Entry
- Identify the architecture problem, decision, or pain signal.
- Gather existing constraints, source evidence, and stakeholder context.
- Select the lightest sufficient method.
Scenes
- PREPARE: Clarify scope, quality attributes, constraints, and artifact target.
- ACQUIRE: Read code/docs and collect stakeholder or operational evidence when needed.
- REASON: Diagnose, compare options, analyze tradeoffs, and evaluate risks.
- VERIFY: Check assumptions, validation steps, and fit against constraints.
- FINALIZE: Produce recommendation, ADR, or architecture artifact.
Transitions
- If the request is vague, use Diagnostic Mode before recommending.
- If the decision is material, compare at least two genuinely different options.
- If risk/quality attributes dominate, use ATAM-style analysis.
- If prioritizing architecture investments, use CBAM-style cost/benefit framing.
- If the decision is final, format it as an ADR.
Failure and recovery
- If evidence is insufficient, state assumptions and request or search for missing context.
- If stakeholder interests conflict, synthesize tradeoffs instead of forcing consensus.
- If the task belongs to another domain, route to the relevant skill.
Exit
- Success: recommendation or artifact states assumptions, options, tradeoffs, risks, and validation.
- Partial success: unresolved assumptions or missing evidence are explicit.
Logical Operations
Actions
| Action | SSL primitive | Evidence |
|---|---|---|
| Classify architecture request | SELECT | Method selection summary |
| Read code/docs/context | READ | Source-grounded architecture evidence |
| Compare options | COMPARE | Design-twice or recommendation mode |
| Infer risks and tradeoffs | INFER | ATAM/CBAM-style analysis |
| Validate decision fit | VALIDATE | Checklist and validation steps |
| Write artifact | WRITE | ADR or architecture result |
| Notify outcome | NOTIFY | Final recommendation summary |
Show full SKILL.md (339 more words)Show less
Tools and instruments
- Local file reading and search for codebase/docs
- Architecture method references and output templates
- Optional stakeholder-agent consultation only when cross-cutting enough to justify cost
Canonical workflow path
rg --files
rg "ADR|architecture|boundary|service|module|dependency|owner|interface" .Then choose Diagnostic, Recommendation, Design-Twice, ATAM-style, CBAM-style, or ADR mode before writing the artifact.
Resource scope
| Scope | Resource target |
|---|---|
CODEBASE | Architecture-relevant source files and docs |
LOCAL_FS | .agents/results/architecture/ artifacts |
MEMORY | Assumptions, option matrix, tradeoff notes |
Preconditions
- The architecture concern or decision boundary is identifiable.
- Relevant context can be read or assumptions can be stated.
Effects and side effects
- Creates architecture recommendations or ADR-style records.
- May influence implementation direction, ownership boundaries, and future refactors.
- Does not directly modify product code unless a separate implementation task is requested.
Guardrails
- Diagnose the architecture problem before selecting a method.
- Use the lightest sufficient methodology for the current decision.
- Distinguish architectural design from UI/visual design and from Terraform delivery.
- Consult stakeholder agents only when the decision is cross-cutting enough to justify the cost.
- Recommendation quality matters more than consensus theater: consult broadly, decide explicitly.
- Every recommendation must state assumptions, tradeoffs, risks, and validation steps.
- Be cost-aware by default: implementation cost, operational cost, team complexity, and future change cost.
- When a decision is material, compare at least two genuinely different options before recommending one.
- Save architecture artifacts to
.agents/results/architecture/.
Method Selection Summary
- Diagnostic Mode: vague pain, unclear architecture symptom
- Recommendation Mode: choose a direction for a concrete architecture decision
- Design-Twice Mode: compare 2+ materially different designs before committing
- ATAM-style Mode: quality-attribute scenarios, tradeoff points, architectural risks
- CBAM-style Mode: cost/benefit prioritization of architecture investments
- ADR Mode: concise final decision record after analysis
References
Follow resources/execution-protocol.md step by step.
See resources/examples.md for output examples.
Use resources/methodology-selection.md to select the right method.
Use resources/stakeholder-synthesis.md when stakeholder consultation is needed.
Use resources/output-templates.md to format the final artifact.
Before submitting, run resources/checklist.md.
- Execution steps:
resources/execution-protocol.md - Checklist:
resources/checklist.md - Examples:
resources/examples.md - Method selection:
resources/methodology-selection.md - Stakeholder protocol:
resources/stakeholder-synthesis.md - Output templates:
resources/output-templates.md - Context loading:
../_shared/core/context-loading.md - Difficulty guide:
../_shared/core/difficulty-guide.md - Reasoning templates:
../_shared/core/reasoning-templates.md - Clarification protocol:
../_shared/core/clarification-protocol.md - Quality principles:
../_shared/core/quality-principles.md
© first-fluke, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 6 other files in benchmarks/runs/oma/.agents/skills/oma-architecture of first-fluke/oh-my-agent.
- SKILL.md
- resources/checklist.md
- resources/examples.md
- resources/execution-protocol.md
- resources/methodology-selection.md
- resources/output-templates.md
- resources/stakeholder-synthesis.md
Open the folder on GitHubat commit b364119
Compare with similar skills
Oma Architecture next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Oma Architecture this skillfirst-fluke/oh-my-agent | 1.3k | — | ~2.1k | Automated safety check: Pass | MIT | |
| Senior Architectalirezarezvani/claude-skills | 28k | 4 repos | ~2.7k | Automated safety check: Pass | MIT | |
| Evolutionary Modular Architecturetech-leads-club/agent-skills | 7k | — | ~3.7k | Automated safety check: Pass | CC-BY-4.0 | |
| Create Vibe Featuremistralai/mistral-vibe | 5.1k | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Designing ArchitectureCloudAI-X/claude-workflow-v2 | 1.4k | 1 repos | ~1.4k | Automated safety check: Pass | MIT | |
| System Architecture DesignerJeffallan/claude-skills | 12k | — | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
Evolutionary Modular Architecture
tech-leads-club/agent-skills
Guides design of modular-monolith platforms with DDD, flat-by-aggregate modules, anti-corruption layers, outbox events and resilience, plus an architecture document with SVG diagrams.
- Official
Create Vibe Feature
mistralai/mistral-vibe
Guides feature work in the Mistral Vibe Python CLI so each change lands in the right module and matches the project's architecture decision records.
Designing Architecture
CloudAI-X/claude-workflow-v2
Designs software architecture and selects appropriate patterns for projects.
System Architecture Designer
Jeffallan/claude-skills
Guides system architecture design end to end: gathering requirements, matching them to a pattern, documenting trade-offs with ADRs, and reviewing.
Light System Design
Light0305/Light-skills
Evidence-based workflow for designing or modernizing a software system: current-state inventory, options, API and schema contracts, migration plans, ADRs and verification.
More from first-fluke/oh-my-agent
All 57 skills in this repoOMA Multi-Agent Orchestration
first-fluke/oh-my-agent
Decomposes a complex feature into tasks, dispatches parallel specialist agents with durable state, and supervises verification, QA review and retries.
OMA Multi-Agent Orchestrator
first-fluke/oh-my-agent
Splits a complex feature into prioritized tasks, spawns specialist CLI subagents in parallel, tracks them through shared memory and verifies each result.
Architecture Decisions and ADRs
first-fluke/oh-my-agent
Evaluates system boundaries and tradeoffs and writes architecture recommendations, option comparisons or ADRs, with a Mermaid diagram when structure changes.
OMA Backend Agent
first-fluke/oh-my-agent
Backend specialist for APIs, database work, authentication and migrations that follows clean architecture with router, service and repository layers.
oma Bootstrap
first-fluke/oh-my-agent
Installs or checks the oma CLI and its runtimes (bun, uv, serena) in a fresh workspace so that oma-* skills can run their commands.
Design-First Brainstorm
first-fluke/oh-my-agent
Explores intent, constraints and alternative approaches before any planning, working through questions one at a time and saving an approved design for later steps.
Related
Categories
Questions about Oma Architecture
What does Oma Architecture do?
Architecture specialist for software/system design, module and service boundaries, tradeoff analysis, and stakeholder synthesis. Oma Architecture is an agent skill from first-fluke/oh-my-agent. Architecture specialist for software/system design, module and service boundaries, tradeoff analysis, and stakeholder synthesis.
When should I use Oma Architecture?
Oma Architecture fits situations like: tasks that involve Architecture decision records; tasks that involve Prioritization frameworks; tasks that involve Microservices.
How do I install Oma Architecture in Claude Code?
Run `npx skills add first-fluke/oh-my-agent --skill oma-architecture -a claude-code`. Or copy the skill folder (benchmarks/runs/oma/.agents/skills/oma-architecture in first-fluke/oh-my-agent) into .claude/skills/oma-architecture in your project. Claude Code loads it when a task matches its description.
How do I install Oma Architecture in Codex?
Run `npx skills add first-fluke/oh-my-agent --skill oma-architecture -a codex`. Or copy the skill folder (benchmarks/runs/oma/.agents/skills/oma-architecture in first-fluke/oh-my-agent) into .agents/skills/oma-architecture in your project. Codex loads it when a task matches its description.
Can I use Oma Architecture in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add first-fluke/oh-my-agent --skill oma-architecture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/oma-architecture, .gemini/skills/oma-architecture, .github/skills/oma-architecture and .opencode/skills/oma-architecture in your project.
What does Oma Architecture need to run?
Going by SKILL.md and its folder, Oma Architecture needs the command-line tools its instructions call (rg).
Does Oma Architecture access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Oma Architecture safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Oma Architecture use?
Oma Architecture is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Oma Architecture use?
About 2.1k tokens (SKILL.md is roughly 8.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Oma Architecture?
Skills that share tags, products or a category with Oma Architecture: Senior Architect (alirezarezvani/claude-skills, 28k stars), Evolutionary Modular Architecture (tech-leads-club/agent-skills, 7k stars), Create Vibe Feature (mistralai/mistral-vibe, 5.1k stars) and Designing Architecture (CloudAI-X/claude-workflow-v2, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Oma Architecture?
first-fluke (a GitHub organization) maintains it in first-fluke/oh-my-agent, which has 1,338 GitHub stars. The repository holds 57 skills in this directory. The repository was last updated on October 9, 2026.
Source: first-fluke/oh-my-agent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.