agentmods.dev

agentation-fix-loop

agentation-fix-loop is an agent for Claude Code from AgentsORG/design-engineering. It costs 74 tokens per session (1,483 once invoked), scanned A, original, MIT.

A repair agent for a two-session Agentation workflow, where one session reviews a running website and marks problems while another applies the fixes. It reads each review note's selector, file path, and criticism, then changes the code and continues through the notes.

In plain words
What is it for?
Use it when an Agentation review session has left annotations on a running development site and you need the corresponding code fixes applied one by one.
Why use it?
It connects visual review comments to the files that need changing, reducing the manual work of finding and applying interface fixes.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; mentions subagents.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is Per-agent identity. Inherits from the repo-root [SOUL.md](../SOUL.md) — this section narrows that to the Session-2 fix loop..

Part of the design-engineering plugin — 1 skill, 10 commands, 10 agents shipped together

not rated 32repo +1 10d ago A scan 74 tokens original MIT

Good fit Use it when an Agentation review session has left annotations on a running development site and you need the corresponding code fixes applied one by one.

Compare 6 agents from other repositories ↓
View source ↗ AgentsORG/design-engineering skills.sh
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/AgentsORG/design-engineering
agentmods
npx agentmods add agents/agentsorg/design-engineering/agentation-fix-loop

Made for: Claude Code.

Or install design-engineering, the plugin that ships this one along with the rest of its 1 skill, 10 commands, 10 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 agentation-fix-loop

README.md
[![agentmods](https://agentmods.dev/badge/agents/agentsorg/design-engineering/agentation-fix-loop/github.svg)](https://agentmods.dev/agents/agentsorg/design-engineering/agentation-fix-loop)
Your own site
<a href="https://agentmods.dev/agents/agentsorg/design-engineering/agentation-fix-loop"><img src="https://agentmods.dev/badge/agents/agentsorg/design-engineering/agentation-fix-loop/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 agentation-fix-loop

Your own site · 80×15
<a href="https://agentmods.dev/agents/agentsorg/design-engineering/agentation-fix-loop"><img src="https://agentmods.dev/badge/agents/agentsorg/design-engineering/agentation-fix-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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,483 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 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.1 $0.00074 $0.01483
Opus 5.5 $0.00030 $0.00593
Sonnet 5.5 $0.00015 $0.00297
Haiku 4.5 $0.00007 $0.00148

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

Security

Grade A, and why

agentation-fix-loop 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.

agents/agentation-fix-loop.md · 96 lines

How it starts

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

agentation-fix-loop

You are the Session-2 fix agent in the [[agentation-workflow]] two-session pattern. Session 1 (critique) walks the localhost UI and adds annotations via Agentation's toolbar. You watch for new annotations and apply the fixes.

Workflow

  1. Verify prerequisites. Before doing anything, confirm:

    • The agentation MCP server is registered with your harness (npx add-mcp agentation or npx agentation-mcp init).
    • The user has a running dev server (npm run dev or equivalent) where Agentation's toolbar can mount.
    • The user is in Session 1 / has annotations to apply, OR has copy-pasted an annotation block manually.

  2. Load the operating context. Read:

    • skills/design-engineering/references/meta/agentation-workflow.md — the canonical workflow document, annotation format, critique style.
    • skills/design-engineering/references/meta/review-format.md — even though Agentation produces its own structured output, your code changes should be defensible in Before/After/Why terms.
    • skills/design-engineering/references/meta/gotchas.md and skills/design-engineering/references/meta/pov.md — installer overrides.

  3. For each annotation, follow this loop: a. Read the annotation via agentation_watch_annotations (MCP tool). Extract: selector, file path, computed styles, critique text, referenced principle. b. Open the file at the path. Find the element by selector or by context from the critique. c. Apply the fix. The critique names the principle (visual hierarchy, whitespace, Gestalt grouping) — translate that to a concrete code change using the relevant skill node. d. Commit with a message: <file>: <one-line summary> (Agentation #<annotation-id>). e. Loop to the next annotation.

  4. Cite the node in the commit message. Every fix references the skill node that informed it: card: tighten shadow per shadows-whisper. This creates a traceable audit log.

  5. Skip annotations that conflict with [[pov]]. If the critique recommends "add a purple gradient" but [[pov]] says "no purple gradients ever," skip with a comment in the annotation thread explaining why.

Read the full file on GitHub · 96 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 · 96 lines · 74 tokens per session scan A d23e392842ef

Subscribe to this mod's changes

agentation-fix-loop is an agent published in the GitHub repository AgentsORG/design-engineering (32 stars, last pushed 10d ago), licensed MIT. It adds 74 tokens to every session and 1,483 once invoked, about $0.0003 per session on Opus 5.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-30.

DebuggingDesign and UXaccessibilityagent-skillsagentationagentic-aidesign-eng
Related

Other agents, from other repositories

form

Visual designer — brand identity, color systems, typography, UI design, and design systems.

tonone-ai/tonone · 19 tokens

nw-diverger

Use before DISCUSS — runs JTBD analysis, competitive research, structured brainstorming, and taste-filtered evaluation to produce 3-5 design directions before the team converges on one. Use when the team has a validated problem but hasn't chosen a solution approach.

nWave-ai/nWave · 57 tokens

designer

Ornamental design specialist for historical and modern style analysis, colorblind-accessible palettes, and AI-assisted image generation using Z-Image.

pjt222/agent-almanac · 29 tokens

css-expert

Expert in modern CSS including CSS Grid, Flexbox, custom properties, container queries, CSS layers, native nesting, modern color spaces, and advanced styling techniques. Specializes in responsive design, accessibility, performance optimization, and CSS architecture for scalable applications. Examples: Context: User…

andisab/swe-marketplace · 393 tokens

fec-ui-checker

Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…

bovinphang/frontend-craft · 89 tokens

design-builder

Use this agent for building production-ready prototypes and implementations from design specs — assembling components into full pages, wiring up interactions, integrating with APIs, setting up project scaffolding, and bridging the gap between design decisions and working software. Dispatch after the design-lead has…

Owl-Listener/designpowers · 85 tokens