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-product-manager.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-product-manager)<a href="https://agentmods.dev/agents/nam-cheol/namba-ai/namba-product-manager"><img src="https://agentmods.dev/badge/agents/nam-cheol/namba-ai/namba-product-manager/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-product-manager"><img src="https://agentmods.dev/badge/agents/nam-cheol/namba-ai/namba-product-manager.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.00370 |
| Opus 5 | $0.00000 | $0.00185 |
| Sonnet 5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
namba-product-manager 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 12d 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
81% identical to namba-backend-architect — 12 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 Product Manager
Use this role when shaping scope, acceptance, and delivery slicing before implementation. 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:
- Translate user goals into concrete scope, constraints, and success criteria.
- Tighten acceptance criteria, non-goals, and rollout boundaries.
- Break large ideas into deliverable slices the main session can schedule.
- Call out UX, data, and operational implications early.
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.
- 12d ago First seen · 22 lines · 0 tokens per session scan A 91c7d48d597e
namba-product-manager is an agent published in the GitHub repository Nam-Cheol/namba-ai (11 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 370 tokens. A static security scan graded it A with 0 findings. It is 81% identical to namba-backend-architect, differing in 12 lines, and is treated as a copy.
Other agents, from other repositories
jira-mutator
Use for Atlassian/Jira write operations via scoped Atlassian MCP write tools — create issue, transition status, add comment, edit fields. Operator confirmation is REQUIRED for every state transition (and any other mutation that changes issue state). Jira access uses runtime-discovered Atlassian MCP write tools; the…
jira-reader
Use for read-only Atlassian/Jira inspection — fetching issues, comments, sprints, and project metadata via Atlassian MCP read tools. Performs no mutations. Jira access uses runtime-discovered Atlassian MCP read tools; the tools: frontmatter narrows declarable tools to Read. Returns structured JSON.
emperor-governor
Resource governance agent. Use to track scope creep, token usage, and project drift. The Emperor's gaze is fixed on the finite—budgets, time, focus. Invoke when: project feels bloated, need objective scope assessment, tracking resource consumption.
amby-pm
Product Manager — AmbyKit role for specify/clarify/revise; use for that perspective.
specifications-tracking-specialist
Specialist for maintaining comprehensive and accurate documentation in HISTORY.md and SPECIFICATIONS.md files. Use proactively after any meaningful codebase changes (e.g. skip documentation changes, logs, formatting) IF THOSE FILES EXISTS, to ensure HISTORY.md and SPECIFICATIONS.md documentation remains complete…
beads-converter-default
Verbatim plan-to-beads converter using the bd CLI. Copies full implementation code, requirements, and exit criteria directly into each bead. Each bead is 100% self-contained - no plan back-references or external lookups needed.