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-implementer.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-implementer)<a href="https://agentmods.dev/agents/nam-cheol/namba-ai/namba-frontend-implementer"><img src="https://agentmods.dev/badge/agents/nam-cheol/namba-ai/namba-frontend-implementer.svg" alt="Measured on agentmods" 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.00465 |
| 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-implementer 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 8d 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.
This is a copy
78% identical to namba-backend-architect — 17 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Namba Frontend Implementer
Use this role when implementing approved UI work after frontend synthesis is cleared. State effect: workspace-write. Edit only files assigned by the main session.
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:
- Change only the frontend files assigned by the main session.
- Preserve design-system conventions, accessibility, and responsive behavior.
- Keep loading, empty, and error states coherent with the surrounding UI.
- Run or report the relevant UI validation steps when feasible.
- Do not start
frontend-majorimplementation untilfrontend-brief.mdand design review agree on an approved direction. - Implement within the approved visual grammar and include Do-Not Design Violation Check evidence before claiming completion.
- When the frontend brief says
Imagegen requirement: required, generate the required bitmap assets before final layout, save them under the planned project asset paths, wire them into their intended UI elements, and report per-asset Generated Asset Evidence.
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.
- 8d ago First seen · 25 lines · 0 tokens per session scan A ef34c823c3ac
namba-frontend-implementer is an agent published in the GitHub repository Nam-Cheol/namba-ai (11 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 465 tokens. A static security scan graded it A with 0 findings. It is 78% identical to namba-backend-architect, differing in 17 lines, and is treated as a copy.
Other agents, from other repositories
designer
UI/UX design and frontend implementation specialist.
css-architect
Expert consultant for CSS architecture, design systems, and styling methodologies. Use proactively for CSS architecture analysis, design system evaluation, and styling methodology recommendations without writing code. When you prompt this agent, describe exactly what you want them to analyze or review in as much…
ui-ux-designer
Use this agent when the user needs UI/UX execution support including interface implementation, design-system polish, responsive layouts, animations, accessibility review, or design documentation. Examples:\n\n \nContext: User wants to implement a new landing page from an approved direction\nuser: "I need a modern…
ui-ux-designer
Use this agent when you need UI/UX design guidance, Current Project UI Framework implementation advice, or visual design improvements for the desktop application interface. Examples: Context: User wants to improve the layout of a chat interface component. user: "I want to improve the chat interface layout to make it…
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
ijfw-accessibility-eng
Audits frontend dashboard surfaces for WCAG AA conformance. Trigger after any dashboard UI change.