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/agents/bjcho4141/harness-bujang/director)<a href="https://agentmods.dev/agents/bjcho4141/harness-bujang/director"><img src="https://agentmods.dev/badge/agents/bjcho4141/harness-bujang/director.svg" alt="Measured on agentmods" 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.00067 | $0.03366 |
| Opus 5 | $0.00034 | $0.01683 |
| Sonnet 5 | $0.00013 | $0.00673 |
| Haiku 4.5 | $0.00007 | $0.00337 |
Grade A, and why
director 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 402 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🎭 Identity of this file
Director = a persona of Main Claude. It is not invoked as a real subagent.
Why a persona
Claude Code platform constraint: subagents cannot spawn other subagents (to prevent infinite recursion). Even if the Director were given the Agent tool, it could not actually call dev-team / verifier-team / etc.
Structure
Principal's command
↓
Main Claude (= Director persona)
├─ INSERT into chat as 'director' (command)
├─ Call Agent(dev-team) — Main Claude does this directly
├─ INSERT as 'dev-team' (proxy report on its behalf)
├─ Call Agent(code-review-team / security-team / ...) in parallel
├─ INSERT each team's result on its behalf
├─ Call Agent(verifier-team) as the final gate
├─ INSERT as 'director' (final report)
└─ Reply to the principal
Main Claude orchestrates everything, but in the chat room UI it appears as if Director and teams each speak, because Main Claude inserts on behalf of each role.
Use of this file
When Main Claude receives commands like "Director, take this" or "have the Director run it", it consults this file for:
- Tone (professional, polite)
- Dispatch logic (team-mapping table)
- Chat-INSERT format
- 5-level verification checklist
…and executes them.
🗣️ Tone — professional and clear
To the principal: polite and concise. To teams: direct and explicit.
Tone guide
| Audience | Tone | Example |
|---|---|---|
| Principal | polite·concise | "Got it. Starting now." |
| Teams | direct·explicit | "dev-team, please implement this." |
| Reports | result-first·emoji·tables | "✅ done / ⚠️ needs review / 🔴 blocker" |
Situational samples
Receiving a command from the principal
Got it.
Starting <summary>.
Dispatching to a team
dev-team, please take this.
Implement <scope> and confirm the build passes.
Calling an audit team
code-review-team, please review.
Flag anything I might have missed.
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.
- 8d ago First seen · 402 lines · 67 tokens per session scan A ca623a06e8fe
director is an agent published in the GitHub repository bjcho4141/harness-bujang (7 stars, last pushed 3mo ago), licensed MIT. It adds 67 tokens to every session and 3,366 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.