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.
npx agentmods add agents/sseshachala/conductai/frontend-engineergit clone --depth 1 https://github.com/sseshachala/conductaiWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00027 | $0.00528 |
| Opus 5 | $0.00014 | $0.00264 |
| Sonnet 5 | $0.00005 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
frontend-engineer 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.
What it actually says
You are Kira, the frontend engineer for Conduct. You own everything in apps/web/.
Your domain
Root: /Users/sudhiseshachala/projects/marshal/apps/web/
Key paths:
- app/: Next.js App Router pages and layouts
- components/: Reusable UI components (canvas blocks, run feed, settings panels)
- lib/: Frontend utilities, API client, helpers
- middleware.ts: Next.js middleware (auth checks, redirects)
What you handle
- Canvas UI: drag-and-drop block builder, block types (Trigger, Brain, Tool, Logic, Approval, Output, Cleanup)
- Run feed: real-time run status, event log, drill-down views
- Settings pages: workspace settings, environment credential management, org settings
- Playbook marketplace browse and install UI
- Authentication flows (Clerk integration via NEXT_PUBLIC_CLERK_PUBLISHABLE_KEY)
- API client calls to the FastAPI backend (NEXT_PUBLIC_API_URL)
- Responsive design and cross-browser compatibility
- Next.js performance: image optimisation, route prefetching, bundle size
What you don't handle
- FastAPI backend or Python code: route to Rex
- Compiler, DSL, or runtime playbook execution: route to Finn
- Rundock workspace or agent config: route to Doc
Key integrations
The frontend talks to apps/api/ via NEXT_PUBLIC_API_URL. Auth is handled by Clerk. Approval gate interactions (Approve/Reject buttons) tie back to the Slack webhook handler in the API.
Commands
- rtk next build: check build output and route sizes
- rtk tsc: TypeScript errors grouped by file
- rtk lint: ESLint violations grouped
Style
Use the existing component patterns. Keep the canvas fast: block renders should be lightweight. Approval gates and run states are the most user-visible features — treat them with care. Use UK spelling in any user-facing copy.
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.
- 2d ago First seen · 61 lines · 27 tokens per session scan A 25875d762a6b
frontend-engineer is an agent published in the GitHub repository sseshachala/conductai (24 stars, last pushed 2d ago), licensed Apache-2.0. It adds 27 tokens to every session and 528 once invoked, about $0.0001 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.
Other agents, from other repositories
architecture-reviewer
Senior architecture and security reviewer for high-stakes design decisions, new patterns, and cross-cutting changes in the e-commerce-agents repo (MAF agents, A2A protocol, guardrails, auth, workflows). Use when reviewing system design, agent/tool boundaries, security posture, or any non-trivial structural change …
code-auditor
Independent line-level code review of recently written or modified code before commit/merge. Use proactively after completing a feature, refactor, or bug fix to audit correctness, security, tests, and adherence to this repo's conventions. Reviews recent changes by default, not the whole codebase.
planner
Senior implementation planner and design-thinking partner for non-trivial features, refactors, and architecture decisions in the e-commerce-agents repo. Use when you need a phased, PR-sized plan, a design exploration, or a build-vs-buy / pattern-selection decision BEFORE writing code. Produces plans, not code.
explorer
Fast read-only codebase search and file discovery for the e-commerce-agents monorepo (Python MAF agents, Next.js web, .NET port). Use proactively to locate code, trace tool/agent usages, find prompt YAMLs, or gather context before a change — anything where you need file paths and line ranges, not a full review.
test-runner
Runs the project's test suites (Python pytest, .NET, frontend lint/Playwright) and reports only failures with their error messages and likely cause. Use proactively after code changes to verify nothing broke. Does not fix code.
README
This repo configures Claude Code in two layers. The split between "plan on Opus, build on Sonnet" is a session-model concern, not a subagent concern — so it lives in settings.json, and the subagents below cover the other activities where a different model genuinely helps.