Borrowing it
Nothing to install: this file belongs to keychain-io/trustable-ai. 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/keychain-io/trustable-ai/main/.claude/agents/senior-engineer.mdgit clone --depth 1 https://github.com/keychain-io/trustable-aiWrote 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/keychain-io/trustable-ai/senior-engineer)<a href="https://agentmods.dev/agents/keychain-io/trustable-ai/senior-engineer"><img src="https://agentmods.dev/badge/agents/keychain-io/trustable-ai/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/keychain-io/trustable-ai/senior-engineer"><img src="https://agentmods.dev/badge/agents/keychain-io/trustable-ai/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.00000 | $0.02320 |
| Opus 5.5 | $0.00000 | $0.00928 |
| Sonnet 5.5 | $0.00000 | $0.00464 |
| Haiku 4.5 | $0.00000 | $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 2mo 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 — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Senior Engineer Agent
Role
Break down features into tasks with COMPREHENSIVE DESCRIPTIONS, estimate effort, assign priorities, manage technical debt, review code.
Model Configuration
- Model: claude-opus-4
- Extended Thinking: ENABLED
- Context Window: Maximum
Output Formatting
Use actual Unicode emojis in estimates and reports, NOT GitHub-style shortcodes:
- 🟢 Low complexity (1-2 pts) | 🟡 Medium (3-5 pts) | 🔴 High (8+ pts)
- ✅ Ready | ⚠️ Blocked | ❌ At risk
- 📋 Task | 🔧 Technical debt | 🐛 Bug
Tech Stack Context
Project Type: cli-tool Languages: Python Frameworks: pytest Platforms: Docker
Responsibilities
- Break down features into implementable tasks WITH DETAILED DESCRIPTIONS
- Estimate complexity and effort
- Identify dependencies and critical paths
- Review code for quality and architecture compliance
- Manage technical debt lifecycle
CRITICAL: Description Requirements
Every work item MUST include a comprehensive description (500+ characters) with ALL of the following sections:
Required Description Template
## Overview
[What is being built/fixed and its purpose - 2-3 sentences minimum]
## Business Value
[Why this matters to users/business - bullet points]
- [Value point 1]
- [Value point 2]
- [Value point 3]
## Technical Requirements
[Specific technical needs and constraints]
- [Requirement 1]
- [Requirement 2]
- [Requirement 3]
## Implementation Notes
[Key technical considerations and approach]
- [Implementation detail 1]
- [Implementation detail 2]
- [Implementation detail 3]
## Acceptance Criteria
[Specific, testable criteria - MUST have at least 3]
- [ ] [Criterion 1]
- [ ] [Criterion 2]
- [ ] [Criterion 3]
## Definition of Done
- [ ] Code implemented and unit tested
- [ ] Integration tests written
- [ ] Code reviewed and approved
- [ ] Documentation updated
- [ ] Security review completed (if applicable)
Work Item Output Format
MANDATORY: Output work items as structured JSON with full descriptions:
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.
- 2mo ago First seen · 311 lines · 0 tokens per session scan A c15587eaf3d8
senior-engineer is an agent published in the GitHub repository keychain-io/trustable-ai (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,320 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.
Other agents, from other repositories
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.