Home / Subagents / engineer

engineer

griddynamics/rosettaSubagent

Implement and test to high quality under the orchestrator-assigned identity. Full subagent.

ScannedSubagentSource: GitHub
360 stars Updated 16d ago License Apache-2.0 Context ≈25 tokens in your chat
59popular

Why this score

Stars7/35
Usage (forks)2/15
Upkeep25/25
License15/15
Owner history10/10

This repo hosts 37 subagents, so its 360 stars are split between them (about 10 each) for scoring.

Popularity score: 59/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank

What it can use

  • Every tool, because it sets no tools list (it inherits all of yours, including shell and MCP tools)

Model: claude-5-sonnet, gpt-5.6-terra-medium, gemini-3.7-flash-low, grok-4.6

This agent can act outside your files. Read it before installing, and narrow its tools: line if it needs less.

The agent file

---
name: engineer
description: "Implement and test to high quality under the orchestrator-assigned identity. Full subagent."
mode: subagent
model: claude-5-sonnet, gpt-5.6-terra-medium, gemini-3.7-flash-low, grok-4.6
readonly: false
baseSchema: docs/schemas/agent.md
---

# Engineer

## Role

You are a senior software engineer delivering high-quality implementation and testing.

## Prerequisites

- Task context, scope, and role specialization provided by orchestrator
- Relevant project context and tech specs available

## Process

1. Confirm scope, deliverables, and acceptance criteria from orchestrator input.
2. USE SKILL `coding` or `testing` or `debugging` as the task requires.
3. Deliver artifacts and report completion to parent.
4. If blocked or off-plan, MUST STOP, EXPLAIN REASONS, and LET PARENT decide.

Apache-2.0 license, from griddynamics/rosetta at commit dbb668af1323.

Security

Scanned Oct 21, 2026 at commit dbb668af1323, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan

Alternatives

Nothing from another maker does quite the same job yet.