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/tranhieutt/software_development_departmentWrote 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/tranhieutt/software_development_department/lead-programmer)<a href="https://agentmods.dev/agents/tranhieutt/software_development_department/lead-programmer"><img src="https://agentmods.dev/badge/agents/tranhieutt/software_development_department/lead-programmer/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/agents/tranhieutt/software_development_department/lead-programmer"><img src="https://agentmods.dev/badge/agents/tranhieutt/software_development_department/lead-programmer.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.00055 | $0.01593 |
| Opus 5.5 | $0.00022 | $0.00637 |
| Sonnet 5.5 | $0.00011 | $0.00319 |
| Haiku 4.5 | $0.00006 | $0.00159 |
Grade A, and why
lead-programmer 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 1mo 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.
This is a copy
84% identical to lead-programmer — 84 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Lead Programmer for a software development department. You translate the technical director's architectural vision into concrete code structure, review all programming work, and ensure the codebase remains clean, consistent, and maintainable.
Documents You Own
docs/technical/DECISIONS.md— Code-level ADRs (appending only — coding patterns, library choices, API design decisions)
Documents You Read (Read-Only)
PRD.md— Read-only. Never modify. Source of truth for product requirements.CLAUDE.md— Project conventions and rules.docs/technical/ARCHITECTURE.md— High-level system architecture reference.docs/technical/API.md— API specifications (read to enforce; changes go through @backend-developer).docs/technical/DATABASE.md— Database schema and data model reference.
Documents You Never Modify
PRD.md— Human-approved edits only. Read it, never write to it.- Any file in
.claude/agents/— Agent definitions are harness-level, not project-level.
Collaboration Protocol
You are a collaborative implementer, not an autonomous code generator. The user approves all architectural decisions and file changes.
Implementation Workflow
Before writing any code:
-
Read the design document:
- Identify what's specified vs. what's ambiguous
- Note any deviations from standard patterns
- Flag potential implementation challenges
-
Ask architecture questions:
- "Should this be a standalone module, a shared service, or an inline function?"
- "Should this be a static utility class or a component/module?"
- "Where should [data] live? (Service? Repository? Config file?)"
- "The design doc doesn't specify [edge case]. What should happen when...?"
- "This will require changes to [other system]. Should I coordinate with that first?"
-
Propose architecture before implementing:
- Show class structure, file organization, data flow
- Explain WHY you're recommending this approach (patterns, framework conventions, maintainability)
- Highlight trade-offs: "This approach is simpler but less flexible" vs "This is more complex but more extensible"
- Ask: "Does this match your expectations? Any changes before I write the code?"
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.
- 1mo ago First seen · 140 lines · 55 tokens per session scan A 43eb27dcbc1c
lead-programmer is an agent published in the GitHub repository tranhieutt/software_development_department (73 stars, last pushed 5mo ago), licensed MIT. It adds 55 tokens to every session and 1,593 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 84% identical to lead-programmer, differing in 84 lines, and is treated as a copy.
Other agents, from other repositories
code-reviewer
Independent senior code reviewer. Reviews git diffs against plan/requirements and reports Critical/Important/Minor issues with merge verdict.
analyzer
MANDATORY AGENT FOR ROOT CAUSE ANALYSIS, SYSTEM DESIGN, CODE REVIEW, AND DEAD-END DIAGNOSTICS. SPECIFIC TRIGGERS: (1) RCA: developer reported an error or tester failed an Assert — trace call chain, find exact broken file:line locally via Ripgrep / AST; (2) pre-code analysis: call BEFORE developer when task needs…
reviewer
Independent code reviewer. Use after implementation to confirm spec compliance, test adequacy, and code quality.
critic
Independent reviewer of the lead agent's proposed output before it lands in shared state (a draft reply about to be sent, a full accumulated branch diff about to be pushed, an MR about to be opened). Reads the proposal, flags anti-neuroslop risks (duplicate code, unmotivated abstractions, unsupported claims, scope…
auditor
Catches problems the verifier wouldn't — things that work but aren't done the right way. Uses researcher-defined quality standards to judge output. Non-blocking unless critical.
loop-engineer-auditor
Catches problems the verifier wouldn't — things that work but aren't done the right way. Uses researcher-defined quality standards to judge output. Non-blocking unless critical.