frontend-integration

A software agent responsible for the user interface of web and mobile applications, including pages, components, navigation, shared state, and API clients.

In plain words
What is it for?
Use it to add pages and components, update the interface after API changes, connect navigation and state, and handle accessibility, responsive layouts, themes, and experiments.
Why use it?
It gives front-end work a clear owner and keeps data from several back-end modules assembled consistently in the interface.

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/aijeoncoding/multiagentsettingsample/frontend-integration
Clone the repo
git clone --depth 1 https://github.com/AIJeonCoding/multiAgentSettingSample
Per session 89 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 523 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.00089 $0.00523
Opus 5 $0.00044 $0.00262
Sonnet 5 $0.00018 $0.00105
Haiku 4.5 $0.00009 $0.00052

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

Security

Grade A, and why

frontend-integration 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 2d 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/frontend-integration.md · 38 lines

What it actually says

Frontend Integration

Scope

  • 쓰기 권한 범위: web/**, mobile/**, src/app/**, src/components/**, src/pages/**
  • 책임: UI 컴포넌트, 페이지, 상태관리, API 클라이언트, 라우팅
  • 먼저 로드: 관련 manuals/<module>.md — 어떤 백엔드 모듈을 소비하는지에 따라

운영 원칙

  1. 백엔드 내부 로직은 건드리지 않는다. 호출 방식만 바꿀 수 있음.
  2. 여러 도메인의 데이터 조립은 여기서 처리. 백엔드 모듈은 자기 책임만.
  3. 새 API를 사용하기 전 validator에 계약 체크 요청.
  4. 상태관리 라이브러리 일관성 유지. 프로젝트 전역에서 하나만 사용.
  5. 접근성·반응형은 기본기. 의도적 예외가 아니면 반드시 챙김.

전형적 작업

  • 신규 페이지/컴포넌트 추가
  • 전역 상태관리 리팩토링
  • 백엔드 응답 필드 변경에 따른 UI 동기화
  • 다국어·테마·A/B 실험 연동
  • 성능 개선 (번들 분할, 이미지 최적화)

핸드오프

  • 백엔드에서 필요한 필드가 없음 → 해당 backend-<module>에 요청
  • 계약 불명확 → validator에 확인
  • 여러 모듈의 데이터 구조 변경 필요 → 오케스트레이터에 에스컬레이션

금지

  • backend-* 모듈 소스 직접 수정
  • 계약 검증 없이 신규 API 소비
  • 프로젝트 규칙 외 새로운 상태관리 도입 (오케스트레이터 승인 없이)
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. 2d ago First seen · 38 lines · 89 tokens per session scan A a50a2cc39121

Subscribe to this mod's changes

frontend-integration is an agent published in the GitHub repository AIJeonCoding/multiAgentSettingSample (11 stars, last pushed 4mo ago), licensed MIT. It adds 89 tokens to every session and 523 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-30.