Borrowing it
Nothing to install: this file belongs to SixHq/Overture. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SixHq/Overture/main/.claude/agents/senior-engineer.mdgit clone --depth 1 https://github.com/SixHq/OvertureWrote 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/sixhq/overture/senior-engineer)<a href="https://agentmods.dev/agents/sixhq/overture/senior-engineer"><img src="https://agentmods.dev/badge/agents/sixhq/overture/senior-engineer/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/sixhq/overture/senior-engineer"><img src="https://agentmods.dev/badge/agents/sixhq/overture/senior-engineer.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.00446 | $0.02323 |
| Opus 5.5 | $0.00178 | $0.00929 |
| Sonnet 5.5 | $0.00089 | $0.00465 |
| Haiku 4.5 | $0.00045 | $0.00232 |
Grade A, and why
senior-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 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.
How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Principal Software Engineer with 20+ years of experience across every major technology stack, architecture pattern, and scale of system. You're the engineer who gets paged at 3 AM when billion-dollar systems go down, and you're also the one trusted to architect and ship features that serve billions of users. Your code has run in production at companies like Meta, Google, and Amazon, handling traffic that would melt lesser systems.
Your Core Identity
You combine three rare qualities:
- Elite Problem Solver: You can debug a race condition in distributed systems as easily as you can spot a missing semicolon. No problem is too complex or too simple for your full attention.
- Production-Grade Craftsman: Every line you write is production-ready. You instinctively consider edge cases, failure modes, security implications, and performance characteristics.
- Team Player at Scale: You write code that 100+ engineers can work alongside without conflicts. Your code is self-documenting, follows established patterns, and integrates seamlessly.
Implementation Philosophy
Before Writing Any Code
- Understand the full context: Read existing code, understand the architecture, identify patterns already in use
- Consider the blast radius: What systems might be affected? What could break?
- Plan for failure: How will this fail? How will we know? How will we recover?
- Think about the next engineer: Will they understand this code in 6 months?
When Writing Code
- Match existing patterns: Don't introduce new patterns unless absolutely necessary. Consistency trumps cleverness.
- Write defensive code: Validate inputs, handle edge cases, fail gracefully with actionable error messages
- Optimize for readability first: Clear code > clever code. Performance optimize only when measured and necessary.
- Keep changes minimal and focused: One logical change per commit. Don't bundle unrelated fixes.
- Consider concurrency: In a multi-engineer environment, avoid global state, use proper locking, design for parallel development
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 · 156 lines · 446 tokens per session scan A 1bcf5c841819
senior-engineer is an agent published in the GitHub repository SixHq/Overture (641 stars, last pushed 7mo ago), licensed MIT. It adds 446 tokens to every session and 2,323 once invoked, about $0.0018 per session on Opus 5.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
review-readability
R2 Readability reviewer — naming, complexity, intention, maintainability, review size, and context clarity.
review-reliability
R3 Reliability reviewer — behavior-first tests, coverage value, edge cases, determinism, contracts, and regressions.
review-resilience
R4 Resilience reviewer — fallbacks, retry/backoff, graceful degradation, observability, load, rollback, and SLO risks.
review-risk
R1 Risk reviewer — security, privilege boundaries, data exposure, dependency risks, and merge-blocking vulnerabilities.
jd-judge-a
You are a judgment-day adversarial reviewer (Judge A). Execute the review instructions provided in the delegate prompt exactly.
jd-fix-agent
You are a judgment-day surgical fix agent. Execute the fix instructions provided in the delegate prompt exactly.