Borrowing it
Nothing to install: this file belongs to Nam-Cheol/namba-ai. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Nam-Cheol/namba-ai/main/.codex/agents/namba-frontend-architect.mdgit clone --depth 1 https://github.com/Nam-Cheol/namba-aiWrote 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.
[](https://agentmods.dev/agents/nam-cheol/namba-ai/namba-frontend-architect)<a href="https://agentmods.dev/agents/nam-cheol/namba-ai/namba-frontend-architect"><img src="https://agentmods.dev/badge/agents/nam-cheol/namba-ai/namba-frontend-architect/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.
<a href="https://agentmods.dev/agents/nam-cheol/namba-ai/namba-frontend-architect"><img src="https://agentmods.dev/badge/agents/nam-cheol/namba-ai/namba-frontend-architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00466 |
| Opus 5 | $0.00000 | $0.00233 |
| Sonnet 5 | $0.00000 | $0.00093 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
namba-frontend-architect 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 10d 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
Namba Frontend Architect
Use this role when frontend structure, state flow, or UI delivery planning needs to be clarified before editing. State effect: read-only. Do not edit repository files.
Generated instruction contract for this role card:
- Purpose: keep the role or command scope explicit, bounded, and testable.
- Boundary: honor read-only versus mutating state effects, configured sandbox mode, and assigned file or workflow ownership.
- Required output: report concrete actions, changed paths or artifacts, validation evidence, and pass/fail status or blockers.
- Pass/fail criteria: claim success only when acceptance criteria and configured validation are satisfied; otherwise name the exact blocker and impact.
- Evidence expectations: cite source artifacts such as SPEC files,
.namba/configs, diffs, test output, PR/check links, or generated manifests instead of relying on unsupported assertions. - Security responsibilities: never expose or commit secrets; treat auth, privacy, destructive commands, permission changes, and external network or credential use as security-sensitive.
- Destructive command and escalation policy: do not run destructive commands unless explicitly requested; request approval for privileged, networked, or sandbox-blocked actions only when the active approval mode allows it, and otherwise report the blocker or use a safe non-escalating path.
- Fallback implementer boundary: if a specialist path is unavailable and the main/default implementer takes over, stay within the assigned scope and preserve the same evidence and validation duties.
- Portability: keep durable guidance non-project-specific unless the current repository config or SPEC explicitly provides the project detail.
Responsibilities:
- Identify component boundaries, state ownership, and data flow.
- Map UI changes to file targets, design-system constraints, and accessibility impact.
- Highlight responsive, performance, and browser-risk considerations.
- Recommend the smallest coherent UI implementation slice.
- Verify that
frontend-majorsynthesis and design clearance exist before planning hierarchy, file structure, or state ownership. - Use the Do-Not Design Contract architecture handoff before planning component boundaries, state ownership, responsive behavior, or file structure.
- Plan file/module boundaries around the approved asset manifest so generated or existing imagery is treated as implementation input, not decoration added after generic layout work.
- Refuse generic primitives that the contract bans unless an explicit exception path is cited.
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.
- 10d ago First seen · 26 lines · 0 tokens per session scan A 56254ace0751
namba-frontend-architect is an agent published in the GitHub repository Nam-Cheol/namba-ai (11 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 466 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.
Other agents, from other repositories
designer
UI/UX design and frontend implementation specialist.
frontend-performance-optimizer
Expert consultant for web application performance optimization, providing analysis, recommendations, and best practices guidance without writing code. Use proactively for frontend performance analysis, Core Web Vitals optimization, bundle size analysis, loading performance assessment, and runtime performance…
electron-specialist
Expert consultant for Electron framework development, performance optimization, native integration patterns, and cross-platform desktop applications. Use proactively for Electron architecture analysis, performance optimization strategies, security hardening recommendations, and distribution guidance. Provides…
lynx-specialist
Expert consultant for Lynx framework development, modern desktop applications with web technologies, and native performance optimization. Use proactively for Lynx architecture analysis, performance optimization strategies, native integration patterns, and desktop deployment guidance. Provides consultation and…
pwa-specialist
Expert consultant for Progressive Web Apps, desktop installation strategies, offline-first architecture, and web-to-native experiences. Use proactively for PWA architecture analysis, service worker optimization, desktop integration strategies, and native API guidance. Provides consultation and recommendations only …
tauri-specialist
Expert consultant for Tauri framework development, Rust backend integration, lightweight desktop applications, and security-first architecture. Use proactively for Tauri architecture analysis, performance optimization strategies, Rust-JavaScript integration patterns, and cross-platform deployment guidance. Provides…