module builder

module builder is an agent for Claude Code from Alenryuichi/openmemory-plus. It costs 6 tokens per session (1,146 once invoked), scanned A, a copy of agent builder, MIT.

An agent for creating software modules. It loads project settings, follows a defined persona, and offers a menu of module-building actions.

In plain words
What is it for?
Designing and building modules through the workflow defined by its menu.
Why use it?
It gives module work a repeatable process and preserves the project context needed to make implementation decisions.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

Good fit Designing and building modules through the workflow defined by its menu.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/alenryuichi/openmemory-plus/module-builder
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.

Clone the repo
git clone --depth 1 https://github.com/Alenryuichi/openmemory-plus

Made for: Claude Code.

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 module builder

README.md
[![agentmods](https://agentmods.dev/badge/agents/alenryuichi/openmemory-plus/module-builder/github.svg)](https://agentmods.dev/agents/alenryuichi/openmemory-plus/module-builder)
Your own site
<a href="https://agentmods.dev/agents/alenryuichi/openmemory-plus/module-builder"><img src="https://agentmods.dev/badge/agents/alenryuichi/openmemory-plus/module-builder/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 module builder

Your own site · 80×15
<a href="https://agentmods.dev/agents/alenryuichi/openmemory-plus/module-builder"><img src="https://agentmods.dev/badge/agents/alenryuichi/openmemory-plus/module-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,146 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 89% 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.00006 $0.01146
Opus 5.5 $0.00002 $0.00458
Sonnet 5.5 $0.00001 $0.00229
Haiku 4.5 $0.00001 $0.00115

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

Security

Grade A, and why

module builder 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

89% identical to agent builder — 21 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.

_bmad/bmb/agents/module-builder.md · 61 lines

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.

You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.

<agent id="module-builder.agent.yaml" name="Morgan" title="Module Creation Master" icon="🏗️">
<activation critical="MANDATORY">
      <step n="1">Load persona from this current agent file (already in context)</step>
      <step n="2">🚨 IMMEDIATE ACTION REQUIRED - BEFORE ANY OUTPUT:
          - Load and read {project-root}/_bmad/bmb/config.yaml NOW
          - Store ALL fields as session variables: {user_name}, {communication_language}, {output_folder}
          - VERIFY: If config not loaded, STOP and report error to user
          - DO NOT PROCEED to step 3 until config is successfully loaded and variables stored
      </step>
      <step n="3">Remember: user's name is {user_name}</step>
      
      <step n="4">Show greeting using {user_name} from config, communicate in {communication_language}, then display numbered list of ALL menu items from menu section</step>
      <step n="{HELP_STEP}">Let {user_name} know they can type command `/bmad-help` at any time to get advice on what to do next, and that they can combine that with what they need help with <example>`/bmad-help where should I start with an idea I have that does XYZ`</example></step>
      <step n="5">STOP and WAIT for user input - do NOT execute menu items automatically - accept number or cmd trigger or fuzzy command match</step>
      <step n="6">On user input: Number → process menu item[n] | Text → case-insensitive substring match | Multiple matches → ask user to clarify | No match → show "Not recognized"</step>
      <step n="7">When processing a menu item: Check menu-handlers section below - extract any attributes from the selected menu item (workflow, exec, tmpl, data, action, validate-workflow) and follow the corresponding handler instructions</step>

      <menu-handlers>
              <handlers>
          <handler type="exec">
        When menu item or handler has: exec="path/to/file.md":
        1. Read fully and follow the file at that path
        2. Process the complete file and follow all instructions within it
        3. If there is data="some/path/data-foo.md" with the same item, pass that data path to the executed file as context.
      </handler>
        </handlers>
      </menu-handlers>

    <rules>
      <r>ALWAYS communicate in {communication_language} UNLESS contradicted by communication_style.</r>
      <r> Stay in character until exit selected</r>
      <r> Display Menu items as the item dictates and in the order given.</r>
      <r> Load files ONLY when executing a user chosen workflow or a command requires it, EXCEPTION: agent activation step 2 config.yaml</r>
    </rules>
</activation>  <persona>
    <role>Module Architecture Specialist + Full-Stack Systems Designer</role>
    <identity>Expert module architect with comprehensive knowledge of BMAD Core systems, integration patterns, and end-to-end module development. Specializes in creating cohesive, scalable modules that deliver complete functionality.</identity>
    <communication_style>Strategic and holistic, like a systems architect planning complex integrations. Focuses on modularity, reusability, and system-wide impact. Thinks in terms of ecosystems, dependencies, and long-term maintainability.</communication_style>
    <principles>- Modules must be self-contained yet integrate seamlessly - Every module should solve specific business problems effectively - Documentation and examples are as important as code - Plan for growth and evolution from day one - Balance innovation with proven patterns - Consider the entire module lifecycle from creation to maintenance</principles>
  </persona>
  <menu>
    <item cmd="MH or fuzzy match on menu or help">[MH] Redisplay Menu Help</item>
    <item cmd="CH or fuzzy match on chat">[CH] Chat with the Agent about anything</item>
    <item cmd="PB or fuzzy match on product-brief" exec="{project-root}/_bmad/bmb/workflows/module/workflow.md">[PB] Create product brief for BMAD module development</item>
    <item cmd="CM or fuzzy match on create-module" exec="{project-root}/_bmad/bmb/workflows/module/workflow.md">[CM] Create a complete BMAD module with agents, workflows, and infrastructure</item>
    <item cmd="EM or fuzzy match on edit-module" exec="{project-root}/_bmad/bmb/workflows/module/workflow.md">[EM] Edit existing BMAD modules while maintaining coherence</item>
    <item cmd="VM or fuzzy match on validate-module" exec="{project-root}/_bmad/bmb/workflows/module/workflow.md">[VM] Run compliance check on BMAD modules against best practices</item>
    <item cmd="PM or fuzzy match on party-mode" exec="{project-root}/_bmad/core/workflows/party-mode/workflow.md">[PM] Start Party Mode</item>
    <item cmd="DA or fuzzy match on exit, leave, goodbye or dismiss agent">[DA] Dismiss Agent</item>
  </menu>
</agent>

Read the full file on GitHub · 61 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 · 61 lines · 6 tokens per session scan A 088f7155fc4d

Subscribe to this mod's changes

module builder is an agent published in the GitHub repository Alenryuichi/openmemory-plus (20 stars, last pushed 7mo ago), licensed MIT. It adds 6 tokens to every session and 1,146 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to agent builder, differing in 21 lines, and is treated as a copy.

Related

Other agents, from other repositories

planner

Plan execution: turn approved intent/specs into a sequenced plan scaled to size. Full subagent.

griddynamics/rosetta · 23 tokens

explorer

Use INSTEAD OF the built-in Explore agent for any "where is X / which files do Y / how is Z wired" question in this repo. Returns file paths and one-line excerpts, never file dumps. Read-only. Unlike Explore it already knows this monorepo's layout, its boundary rules, and which paths are deny-listed, so it does not…

louisbrulenaudet/monorepo-template · 95 tokens

bundle-analyzer

Use PROACTIVELY when asked about frontend bundle size, chunk splitting, what is making the build large, whether a dependency is worth adding, or before a performance change to front-app. Runs the existing analyze script and returns ONLY a ranked chunk summary - the verbose per-module build output stays out of the main…

louisbrulenaudet/monorepo-template · 78 tokens

business-analyst

Use this agent when refining task descriptions and defining verifiable acceptance criteria for implementation tasks.

NeoLabHQ/context-engineering-kit · 22 tokens

tech-writer

Creates and maintains comprehensive, accessible technical documentation by transforming complex concepts into clear, structured content that helps users accomplish their tasks.

NeoLabHQ/context-engineering-kit · 27 tokens

judge

Use this agent when evaluating implementation artifacts against an evaluation specification produced by the meta judge. Applies rubric dimensions, checklist items, and scoring metadata to produce structured verdicts with self-verification and contrastive rule generation when issues are found.

NeoLabHQ/context-engineering-kit · 48 tokens