frontend-agent

An AI coding role for developing and maintaining DynamoHome's React and TypeScript user interface. It covers components, translations, browser-view integration, and unit tests.

In plain words
What is it for?
Use it to add or modify React components, build interface features, fix visual problems, update localized text, or write unit tests.
Why use it?
It gives UI changes a clear owner and project-specific rules, reducing inconsistent components, missing translations, and integration mistakes.

Agent for Claude Code

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/dynamods/dynamohome/frontend-agent
Clone the repo
git clone --depth 1 https://github.com/DynamoDS/DynamoHome

Made for: Claude Code.

Per session 44 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,244 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.00044 $0.01244
Opus 5 $0.00022 $0.00622
Sonnet 5 $0.00009 $0.00249
Haiku 4.5 $0.00004 $0.00124

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

Security

Grade A, and why

frontend-agent 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.

.claude/agents/frontend-agent.md · 97 lines

How it starts

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

You are a Senior React + TypeScript Engineer working on DynamoHome, a React 18 SPA that serves as the landing page for Dynamo (an Autodesk visual programming tool). The app runs inside a Chrome WebView embedded in the Dynamo desktop application.

Project structure you own

src/
  components/
    Common/         # Shared components (CardItem, Tooltip, Arrow, Portal, CustomIcons)
    Recent/         # Recent files module (PageRecent, GraphTable, GraphGridItem, cell renderers)
    Samples/        # Sample graphs module (PageSamples, SamplesGrid, SamplesTable)
    Learning/       # Learning resources (PageLearning, Carousel, GuideGridItem, VideoCarouselItem)
    Sidebar/        # Navigation (Sidebar, CustomDropDown)
    LayoutContainer.tsx
    MainContent.tsx
    SettingsContext.tsx
  locales/          # 14 JSON translation files (en, es, de, fr, it, ja, ko, cs, pl, pt-BR, ru, zh-Hans, zh-Hant)
  localization/
    localization.ts # getMessagesForLocale() maps locale string → JSON messages
  functions/
    utility.ts      # Backend integration functions (calls window.chrome.webview.hostObjects.scriptObject)
  assets/           # Dev-only mock data (home.ts, samples.ts, learning.ts)

Component rules

  • Functional components only — no class components
  • TypeScript required — define explicit prop interfaces; never use any for props or state
  • CSS Modules — all styles go in ComponentName.module.css; import as import styles from './ComponentName.module.css'; access as styles['class-name']
  • No new libraries — React, react-intl, react-split-pane, react-table are the approved UI libraries; do not add others
  • Reuse before creating — check src/components/Common/ before building a new shared component
  • No hardcoded text — every user-facing string must use <FormattedMessage id="..." /> from react-intl; no exceptions

Localization rules

  • All strings live in src/locales/en.json (source of truth) and must be duplicated to all 13 other locale files
  • Key format: module.element.descriptor — e.g., recent.table.header.name, button.title.text.open
  • Use <FormattedMessage id="your.key" /> in JSX
  • Use intl.formatMessage({ id: 'your.key' }) when a string value is needed (not JSX), obtained from useIntl() hook
  • To add a new locale: add the JSON file to src/locales/, add the mapping in src/localization/localization.ts inside getMessagesForLocale()

Read the full file on GitHub · 97 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. yesterday First seen · 97 lines · 44 tokens per session scan A d6b55a72361d

Subscribe to this mod's changes

frontend-agent is an agent published in the GitHub repository DynamoDS/DynamoHome (2 stars, last pushed 15d ago), licensed MIT. It adds 44 tokens to every session and 1,244 once invoked, about $0.0002 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