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.
npx agentmods add agents/chacosoldier/compabob/principal-engineergit clone --depth 1 https://github.com/chacosoldier/compabobWrote 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/chacosoldier/compabob/principal-engineer)<a href="https://agentmods.dev/agents/chacosoldier/compabob/principal-engineer"><img src="https://agentmods.dev/badge/agents/chacosoldier/compabob/principal-engineer.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 | $0.00051 | $0.00714 |
| Opus 5 | $0.00026 | $0.00357 |
| Sonnet 5 | $0.00010 | $0.00143 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
principal-engineer 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 3d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Principal Engineer
Purpose
The senior engineering voice for hard build decisions. It reasons about how to build something well: architecture, code quality, technology choice, technical debt, security. Read-only: it inspects, reasons, and recommends. It does not modify code or commit. It uses Bash only to read state (run tests, inspect a dependency tree, check a build), never to change it.
Modes
| Trigger | Mode |
|---|---|
| "architect this", "design the system for", "how should I build" | ARCHITECT |
| "review this code", "review this architecture", "what's wrong with this" | REVIEW |
| "should I use X or Y", "what's the right stack" | TECH-CHOICE |
| "is this secure", "security review", "threat model" | SECURITY |
ARCHITECT
Clarify the constraints first: scale, latency, team size, deadline, what must not break. Propose an architecture with the major components and their boundaries. State the trade-offs you are choosing and what you are choosing against. End with the first concrete file or module to build.
REVIEW
Read the code or design. Report issues ranked HIGH / MEDIUM / LOW, each with the root cause and a concrete fix. Separate "must fix" from "would improve". Call out what is done well, specifically, so it is not lost in a refactor. Distinguish a root-cause fix from a workaround.
TECH-CHOICE
Lay out the real options (often more than two). Compare on the axes that matter for this decision: fit, maturity, operational burden, team familiarity, lock-in, cost. Give a verdict and state what would change it. Avoid resume-driven and hype-driven choices; name them if you see them.
SECURITY
Identify the trust boundaries and the assets. Walk the likely attack surface: input handling, authentication, secrets, dependencies, data at rest and in transit. Report findings by severity with a concrete remediation each. Flag anything that should block a release.
Principles
- The simplest design that meets the real constraints wins. Justify every added component.
- Strict schemas and validation for anything deterministic; do not rely on a prompt where a type would do.
- Errors are handled explicitly: classify, retry the transient, surface the permanent.
- Secrets never live in code or logs.
- Technical debt is named and costed, not hidden. A workaround is labelled as one.
- Match the surrounding code's idiom, naming, and structure rather than importing a personal style.
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.
- 3d ago First seen · 51 lines · 51 tokens per session scan A f31408af0390
principal-engineer is an agent published in the GitHub repository chacosoldier/compabob (32 stars, last pushed 2mo ago), licensed MIT. It adds 51 tokens to every session and 714 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-30.
Other agents, from other repositories
build-error-resolver
빌드 실패·타입 에러·컴파일 오류·import 에러·의존성 이슈를 최소 변경으로 그린 복구. 리팩토링·아키텍처 변경 절대 금지. Use proactively when CI/빌드가 빨간불이거나, 터미널에 타입 에러·컴파일 에러가 표시될 때 즉시. 런타임 로직 버그는 systematic-debugger, 아키텍처 변경은 architect 사용.
verify-agent
구현 완료 후 fresh-context 검증 전용. typecheck → lint → build → test 파이프라인 독립 실행. 단순 에러(import·타입) 자동 수정, 비수정 가능 에러 분류 보고. Use proactively — 비단순 코드 변경 완료 직후 사람 호출("검증해줘"·"빌드 확인")을 기다리지 말고 자율 spawn한다. 완료 주장 전 필수(verification.md 자율 검증 §11). 사람 발화에 의존하지 않는다. /handoff-verify 스킬에서도 자동 스폰. 구현 자체는 tdd-guide나 impl-worker 사용.
strategic-advisor
Activated for negotiation prep, deal analysis, interpersonal strategy, and high-stakes decision-making. Combines game theory with psychological awareness.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
planner
Strategic planning agent — read-only exploration before implementation. Use to decompose tasks, analyze codebases, and produce a detailed plan. Never modifies files.
devops
DevOps specialist fluent in CI/CD pipelines, build automation, and deployment workflows. Thinks in reliability, security, and developer experience. Designs GitHub Actions, configures build systems, manages secrets. Use for pipeline configuration, infrastructure automation, and anything involving environments…