electrobun-architect

An architecture-planning step for the Electrobun software development process, covering desktop windows and views. It turns a research report into a specification for the layout, communication between parts, files, settings, and affected files.

In plain words
What is it for?
Use it to plan a new desktop window or view, define RPC communication between interface and application code, outline the project files and configuration, and assess the change’s blast radius.
Why use it?
It helps reveal the work and dependencies before implementation begins, including which files will change and why.

Agent

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.

agentmods
npx agentmods add agents/dexploarer/plugin-electrobun-dev/electrobun-architect
Clone the repo
git clone --depth 1 https://github.com/Dexploarer/plugin-electrobun-dev
Per session 74 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,396 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found 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 $0.00074 $0.01396
Opus 5 $0.00037 $0.00698
Sonnet 5 $0.00015 $0.00279
Haiku 4.5 $0.00007 $0.00140

Measured yesterday against content hash cfe01b134378, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

agents/electrobun-architect.md · 165 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. yesterday First seen · 165 lines · 74 tokens per session scan A cfe01b134378

Subscribe to this mod's changes

electrobun-architect is an agent published in the GitHub repository Dexploarer/plugin-electrobun-dev (5 stars, last pushed 5mo ago), with no licence file. It adds 74 tokens to every session and 1,396 once invoked, about $0.0004 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-08-31.

Related

Other agents, from other repositories

tasks-to-chats-migration

The Tasks API (/api/v2/tasks) and the Chats API (/api/v2/chats) serve similar goals (programmatic access to AI-powered coding agents) but they differ significantly in architecture, capabilities, and usage patterns.

coder/coder · 0 tokens

models

Administrators configure LLM providers from Admin settings > AI and Coder Agents models from Admin settings > AI > Models. Providers and centrally managed credentials are deployment-wide settings managed by platform teams. Each model belongs to an organization. Each organization has its own model list. Developers…

coder/coder · 0 tokens

index

Coder Agents is a chat interface and API for delegating development work and research to coding agents in your Coder deployment. Developers describe the work they want done, and Coder Agents handles selecting a template, provisioning a workspace, and executing the task.

coder/coder · 0 tokens

getting-started

This guide walks platform teams and administrators through setting up Coder Agents, preparing your deployment, and running your first Coder Agent.

coder/coder · 0 tokens

extending-agents

Workspace templates can extend the agent with custom skills and MCP tools. These mechanisms let platform teams provide repository-specific instructions, domain expertise, and external tool integrations without modifying the agent itself.

coder/coder · 0 tokens

licensing-usage

Coder Agents licensing controls concurrent agent activity and Agent Time usage across your deployment.

coder/coder · 0 tokens