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/.agents/skills/namba-workflow-execution/SKILL.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/skills/nam-cheol/namba-ai/namba-workflow-execution)<a href="https://agentmods.dev/skills/nam-cheol/namba-ai/namba-workflow-execution"><img src="https://agentmods.dev/badge/skills/nam-cheol/namba-ai/namba-workflow-execution/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/skills/nam-cheol/namba-ai/namba-workflow-execution"><img src="https://agentmods.dev/badge/skills/nam-cheol/namba-ai/namba-workflow-execution.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.00022 | $0.00632 |
| Opus 5 | $0.00011 | $0.00316 |
| Sonnet 5 | $0.00004 | $0.00126 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
namba-workflow-execution 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 9d 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
Use this skill when implementing a SPEC package.
State effect: mutating SPEC execution workflow. Read-only only while inspecting the SPEC package before implementation.
Generated instruction contract for this repo skill:
- 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.
Execution pattern:
- Read
.namba/specs/<SPEC>/spec.md - Read
.namba/specs/<SPEC>/plan.md - Read
.namba/specs/<SPEC>/acceptance.md - Read
.namba/specs/<SPEC>/reviews/readiness.mdwhen present so advisory review status informs execution - Read
.namba/specs/<SPEC>/frontend-brief.mdwhen present and treat it as the canonical frontend gate contract - If the SPEC is explicitly
frontend-major, stop and route back to research/synthesis when the frontend gate is incomplete, invalid, or contradicted by design-review summaries - Implement the work directly in the current Codex session
- For browser-rendered frontend changes, use managed server lifecycle, inspect rendered DOM state, capture screenshots, record console errors, and prefer Playwright checks when practical
- Run configured validation commands
- Summarize results in
.namba/logsand sync artifacts
Collaboration defaults: use a dedicated branch from main for the SPEC, open the PR into main, write the PR in Korean, and request Codex review only when namba pr --review or queue --review is explicit; use @codex review as the request command.
Do not call namba run from inside Codex unless the user explicitly requests the non-interactive CLI runner.
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.
- 9d ago First seen · 36 lines · 22 tokens per session scan A 04884807c476
namba-workflow-execution is a skill published in the GitHub repository Nam-Cheol/namba-ai (11 stars, last pushed 17d ago), licensed MIT. It adds 22 tokens to every session and 632 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 skills, from other repositories
agf
Find local coding-agent sessions, inspect bounded metadata or summaries, and prepare a read-only resume plan with AGF. Use for finding prior work across agent CLIs, not for executing agents, deleting sessions, or reading full transcripts.
dynamic-resources
Example skill loaded from resourcesdiscover.
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…
swarm-pr-review
Run a graph-guided, tool-augmented PR review using context packing, parallel exploration, mandatory repository-agnostic risk-family coverage with dispatch scaled to diff size and risk, independent reviewer validation, critic challenge, and metrics writeback. Use for deep pull request review with low false-positive…
bundle-safety
Bundle transform safety — minification variant selection, consumer-constraint verification, identifier preservation, and namespace re-export coverage for build output.