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-fix/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-fix)<a href="https://agentmods.dev/skills/nam-cheol/namba-ai/namba-fix"><img src="https://agentmods.dev/badge/skills/nam-cheol/namba-ai/namba-fix/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-fix"><img src="https://agentmods.dev/badge/skills/nam-cheol/namba-ai/namba-fix.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.00019 | $0.00713 |
| Opus 5.5 | $0.00008 | $0.00285 |
| Sonnet 5.5 | $0.00004 | $0.00143 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
namba-fix 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 2mo 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
State effect: mixed. Help/probe paths are read-only; direct repair mutates the current workspace; --command plan creates a bugfix SPEC.
Generated instruction contract for this command 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.
Use this skill when the user explicitly says $namba-fix, namba fix, or asks to repair a bug through Namba.
Behavior:
- Prefer the installed
namba fixCLI when available. - Treat
namba fix "<issue description>"as the default direct-repair path in the current workspace. - Use
namba fix --command run "<issue description>"when the user wants the explicit direct-repair form. - Use
namba fix --command plan "<issue description>"when the user wants a reviewable bugfix SPEC package under.namba/specs/via the same dedicated-branch planning contract. - For
namba fix --command plan, run the same clarification gate asnamba planandnamba harnessbefore reading project docs, checking Git state, or running the CLI. Ask 1-3 concise questions first when the issue, target surface, scope, constraints, acceptance criteria, or validation are unclear. - When clarification is needed for the planning path, prefer Codex Plan mode and pass only the refined Goal/Scope/Constraints/Acceptance description to
namba fix --command plan "<refined issue description>". - Use
--current-workspaceonly withnamba fix --command planwhen the user intentionally wants to scaffold on the current branch without creating a dedicated SPEC branch. - Do not create planning worktrees for this path; worktrees are reserved for temporary overlapping
namba run SPEC-XXX --parallelexecution. - Keep CLI help and flag probing read-only;
namba <command> --help,namba <command> -h, andnamba help <command>must not mutate repository state. - Keep direct repairs small, add targeted regression coverage, run validation, and finish with
namba sync.
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.
- 2mo ago First seen · 32 lines · 19 tokens per session scan A 20d2370a539e
namba-fix is a skill published in the GitHub repository Nam-Cheol/namba-ai (11 stars, last pushed 12d ago), licensed MIT. It adds 19 tokens to every session and 713 once invoked, about $0.0001 per session on Opus 5.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
autofix
Review and repair current local changes until they converge, or run Qwen Code Autofix issue and review workflows from GitHub Actions.
assess-findings
Triage static analysis findings, grade them against recorded decisions, and accept noise or irrelevant items.
dekko-verify
Sanity-check a suspiciously low or zero call-graph result from dekko (getcallers, getcallees, findusages, impactedtests, unused) before concluding "no callers" or "dead code," or a heritage/throws-provenance result (query supertypes, query subtypes, query throws) that labels something (external) when you expect it to…
trace-mcp-refactoring
Safe refactoring workflow using trace-mcp — assess risk, find candidates, check impact, and rename symbols across all files without missing import sites or cross-file references.
autofix-pr
Watch a pull request and fix it from a worktree of its own - CI failures, review feedback from trusted authors and merge conflicts are fixed, pushed to the PR branch and answered on the PR under the user's git and gh identity. Usage - /autofix-pr [ | ] [--once] [--every ] [--no-reply] [--yes] [instructions]…
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.