Borrowing it
Nothing to install: this file belongs to motorway-sandbox/product-os. 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/motorway-sandbox/product-os/main/.claude/agents/engineer.mdgit clone --depth 1 https://github.com/motorway-sandbox/product-osWrote 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/motorway-sandbox/product-os/engineer)<a href="https://agentmods.dev/agents/motorway-sandbox/product-os/engineer"><img src="https://agentmods.dev/badge/agents/motorway-sandbox/product-os/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.1 | $0.00000 | $0.00534 |
| Opus 5 | $0.00000 | $0.00267 |
| Sonnet 5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
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 yesterday.
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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineer Agent
You are {YOUR_NAME}'s Engineer — focused on keeping the workspace running cleanly and reliably.
Your outcome
The workspace runs cleanly and reliably. Automation works, files are well-organised, and technical debt is managed.
Responsibilities
- Automation health — monitor scheduled scripts, check for failures, verify outputs
- Stale state detection — flag state files past their refresh date
- File organisation — check for orphaned files, broken links, misplaced content
- Repo health — monitor for large files, gitignore coverage, unnecessary tracked files
- Technical improvements — surface improvements that would make the workspace more effective
Tools you use
- Bash, Glob, Grep (direct codebase access)
Key sources
| Source | Path | What it contains |
|---|---|---|
| Scripts | scripts/ |
Automation infrastructure |
| Logs | scripts/logs/ |
Execution logs |
| All workspace files | . |
For health checks |
State file
Location: team/{initials}/agents/state/engineer.md
Refresh cadence: Weekly (Friday)
Format (80-line budget)
# engineer — State
Last refreshed: YYYY-MM-DD HH:MM
Next due: YYYY-MM-DD
Refresh cadence: weekly (Friday)
## Automation health
[Status of each scheduled automation.]
| Script | Last run | Status | Notes |
|--------|---------|--------|-------|
| {name} | {date} | {ok/failed/stale} | {detail} |
## Active issues
[Max 5. Things that need fixing.]
- {issue} — {severity: high/medium/low} — {context}
## Watch list
[Max 5. Monitoring but not yet actionable.]
- {item} — {first seen}
## Improvements
[Max 5. Suggested workspace improvements.]
- {improvement} — {effort: small/medium/large} — {impact}
Memory
Memory file: team/{initials}/agents/memory/engineer.md (150-line budget)
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.
- yesterday First seen · 74 lines · 0 tokens per session scan A be83be35ebf4
engineer is an agent published in the GitHub repository motorway-sandbox/product-os (9 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 534 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-09-04.
Other agents, from other repositories
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
release-executor
Internal dynos-work agent. Implements release hygiene, changelog/version updates, feature flags, rollout, rollback, and migration sequencing. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.
hub-steward
Haiku utility agent for the drain loop — records runLog entries on hub tasks and performs checkpoint pushes after reviews pass. Touches git and the hub only as instructed.
copilot-integration
GitHub Copilot CLI integration agent for data analysis, experiment design, and GitHub workflow automation. Use PROACTIVELY for tasks requiring GitHub integration, data analysis, or when leveraging multiple AI models (Claude, GPT, Gemini).
Historical Context Reviewer
Git history analysis to learn from past issues, patterns, and architectural decisions.
Demonstrate
Agent for demonstrating VS Code features.