Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/bjcho4141/harness-bujangWrote 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/commands/bjcho4141/harness-bujang/bujang-init)<a href="https://agentmods.dev/commands/bjcho4141/harness-bujang/bujang-init"><img src="https://agentmods.dev/badge/commands/bjcho4141/harness-bujang/bujang-init/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/commands/bjcho4141/harness-bujang/bujang-init"><img src="https://agentmods.dev/badge/commands/bjcho4141/harness-bujang/bujang-init.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.00035 | $0.00417 |
| Opus 5 | $0.00017 | $0.00209 |
| Sonnet 5 | $0.00007 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
bujang-init 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
/bujang-init
You are about to install the Harness-Bujang harness into the current project.
Action — run the CLI
The published harness-bujang package on npm handles all the install logic (project detection, agent copy, CLAUDE.md merge, learning log seed, extra-tool adapters). Run it via the user's shell:
npx harness-bujang@latest init
The CLI is interactive when stdin is a TTY: it prompts for:
- Agent language (
en/ko) - Extra tool adapters (Cursor / Cline / Aider / Codex / Gemini — multi-select)
- Per-tool model preset (balanced / keep / cost / quality / custom)
For non-interactive runs (CI / scripts), pass --yes:
npx harness-bujang@latest init --yes --lang=ko
After install
- Restart Claude Code — fully quit and reopen in this folder. Agents register only at session start, so the new director + teams won't be visible until you restart.
- Open the chat room — run
/open-chatto launch the standalone viewer athttp://localhost:7777(server backgrounds, browser auto-opens). - Optional: run
/bujang-statusto verify everything landed correctly, and openCLAUDE.mdto review the## 하네스 엔지니어링(or## Harness Engineering) section that was appended.
Idempotence
Re-running /bujang-init is safe — the CLI skips files that already exist unless --yes is passed. Use --yes to overwrite all agent files with the latest versions (e.g., after harness-bujang is upgraded).
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 · 38 lines · 35 tokens per session scan A 79ef20522fc2
bujang-init is a command published in the GitHub repository bjcho4141/harness-bujang (7 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 417 once invoked, about $0.0002 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.