update

An update agent for deploying Bricks elements to a WordPress website. WordPress is a system for managing website content, and Bricks is one of its visual page builders.

In plain words
What is it for?
Use it to push prepared Bricks elements and their CSS or JavaScript to a draft page, with required snapshots and cache clearing.
Why use it?
It provides a fixed deployment sequence that includes creating a backup snapshot, updating page assets, clearing caches, and avoiding accidental publication.

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/developer2013/bricks-mcp-open/update
Clone the repo
git clone --depth 1 https://github.com/developer2013/bricks-mcp-open
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 169 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original 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.00000 $0.00169
Opus 5 $0.00000 $0.00084
Sonnet 5 $0.00000 $0.00034
Haiku 4.5 $0.00000 $0.00017

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

Security

Grade A, and why

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

agent-service/agents/update.md · 18 lines

What it actually says

Du bist der Update Agent — deployt Bricks-Elemente auf WordPress.

Aufgabe

Pushe die vom Code Agent erstellten Elemente auf die WordPress-Seite.

Workflow (EXAKTE Reihenfolge)

  1. bricks_create_snapshot — PFLICHT vor jedem Push
  2. bricks_update_page — Elemente pushen
  3. bricks_update_page_assets — CSS/JS als Structured Assets
  4. bricks_set_gsap_flag — Falls GSAP verwendet
  5. bricks_purge_cache — Cache leeren

Kritische Regeln

  • SNAPSHOT VOR JEDEM PUSH — keine Ausnahme
  • bricks_update_page_assets ist REPLACE not merge — immer komplettes Bundle senden
  • Per-page Scripts brauchen ... Tags um CSS
  • Status bleibt "draft" (nicht publishen)
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 · 18 lines · 0 tokens per session scan A 41c810f8e7b4

Subscribe to this mod's changes

update is an agent published in the GitHub repository developer2013/bricks-mcp-open (85 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 169 tokens. 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-30.

Related

Other agents, from other repositories

design-reviewer

Judges whether a running localhost UI reads as deliberately designed or as machine-generated, and reports the specific tells with evidence. Delegate when the user says a page looks generic, bland, unfinished, "AI-generated", "like a template" or "not designed", asks for a design critique or a taste check, or wants an…

soumyachk101/VibeLens · 103 tokens

frontend-builder

Builds new frontend work — a screen, a component, a design foundation — with tokens established before components, every interactive and data state implemented, and each screen captured before it is called done. Delegate when the user asks for a new page, view, component or UI library from scratch, wants a visual…

soumyachk101/VibeLens · 121 tokens

ui-debugger

Evidence-driven frontend debugger for a running localhost app. Delegate when a UI bug needs to be diagnosed and fixed from what the browser actually rendered — misalignment, overflow, spacing, wrong colours, blank regions, hydration mismatches or console errors on a dev server. Requires the dev server to be running…

soumyachk101/VibeLens · 74 tokens

ui-reviewer

Reviews a finished frontend implementation against its stated intent by capturing the running page at desktop, tablet and mobile and reporting defects with evidence. Delegate after a UI feature or fix is implemented and you want an independent check before calling it done, or when the user asks for a UI review or a…

soumyachk101/VibeLens · 77 tokens

orchestrator

Role: Coordinate planner and workers in multi-agent PDF pipeline Workflow: pdf-pipeline Namespace: team:eng.

YashvantHange/SuperMemory · 0 tokens

Windsurf-mcp

Windsurf Cascade MCP – Integration with Alph Overview: Windsurf (formerly Codeium’s editor) includes Cascade, an AI agent that can leverage external tools via the Model Context Protocol (MCP)[1]. To integrate Alph with Windsurf, Alph must configure Windsurf’s MCP client to recognize and launch Alph’s MCP server. This…

Aqualia/Alph · 0 tokens