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-status)<a href="https://agentmods.dev/commands/bjcho4141/harness-bujang/bujang-status"><img src="https://agentmods.dev/badge/commands/bjcho4141/harness-bujang/bujang-status/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-status"><img src="https://agentmods.dev/badge/commands/bjcho4141/harness-bujang/bujang-status.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.00034 | $0.00440 |
| Opus 5 | $0.00017 | $0.00220 |
| Sonnet 5 | $0.00007 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
bujang-status 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 11d 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-status
Print a structured status report of the harness install in the current project.
Action — run the CLI status check
The harness-bujang CLI on npm runs all the install verification (agents, CLAUDE.md section, placeholder check, learning log, chat DB). Run:
npx harness-bujang@latest status .
This prints a summary like:
📋 Harness-Bujang status — <project>
Agents
✓ director.md
...
CLAUDE.md
✓ Section present, no unfilled placeholders
Learning log
✓ docs/AGENT_LEARNING_LOG.md
Chat room (.harness/chat.db)
✓ present — open with: bujang chat (or - not yet created)
Overall: 🟢 healthy / 🟡 partial / 🔴 not installed
Recent chat activity (extra)
The CLI does NOT query the chat database. To read recent harness_messages entries from the local SQLite chat DB:
sqlite3 .harness/chat.db \
"SELECT created_at, from_role, to_role, substr(body, 1, 60) FROM harness_messages ORDER BY id DESC LIMIT 10"
After collecting the data, format it into a Recent chat (last N): block and append it under the CLI's output.
When status reports issues
- If agents are missing → suggest
/bujang-init(ornpx harness-bujang@latest init --yesto overwrite) - If CLAUDE.md section missing → same
- If
.harness/chat.dbnot yet created → suggest/open-chat(ornpx harness-bujang chat --create) to create it on first run
Print a single-line fix suggestion for each red/yellow item — never leave the user guessing what to do next.
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.
- 11d ago First seen · 54 lines · 34 tokens per session scan A 8a6dee26ddab
bujang-status is a command published in the GitHub repository bjcho4141/harness-bujang (7 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 440 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.