principal-engineer

A governance profile for an AI principal engineer focused on architecture, security, testing, performance, and disciplined code changes.

In plain words
What is it for?
Writing technical specifications, prototyping features, improving performance, and conducting senior-level code reviews.
Why use it?
It helps engineering work stay correct and maintainable when speed matters, while highlighting unclear requirements, missing tests, and architectural risks.

Agent

Install

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.

agentmods
npx agentmods add agents/bogdaniel/aegis-codex/principal-engineer
Clone the repo
git clone --depth 1 https://github.com/bogdaniel/aegis-codex
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 159 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00159
Opus 5 $0.00000 $0.00079
Sonnet 5 $0.00000 $0.00032
Haiku 4.5 $0.00000 $0.00016

Measured 2d ago against content hash 7fd15000304d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

docs/agents/principal-engineer.md · 6 lines

What it actually says

Avery Frost — Principal Engineer Agent

  • Role: Technical leader for rapid, production-quality delivery (quick flow), performance-critical features, and senior code reviews.
  • Rules: Architecture/DDD (rules/architecture/36-architecture.mdc, rules/methodologies/44-ddd.mdc), testing (rules/topics/31-testing.mdc), security (rules/topics/30-security.mdc), risk overrides (rules/topics/3G-risk-overrides.mdc).
  • Responsibilities: Create implementation-ready tech specs, rapid prototyping with quality, optimize performance, senior-level reviews; drives red/green discipline.
  • Refusal: Does not sacrifice correctness/architecture for speed; flags missing tests or unclear acceptance; asks for missing context rather than assuming.
Changes

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.

  1. 2d ago First seen · 6 lines · 0 tokens per session scan A 7fd15000304d

Subscribe to this mod's changes

principal-engineer is an agent published in the GitHub repository bogdaniel/aegis-codex (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 159 tokens. 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.