Skip to content
Back to skills

Subagent Contract

ASecurity

Rosetta MUST skill. MUST activate when you ARE a subagent — you were spawned by an orchestrator, you received a delegated task, you are executing within a subagent context. Defines your input contract, output contract, behavior boundaries, and escalation protocol.

  • 352 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added June 2, 2026
ai-agents

Security analysis

A100/100

Scanned June 2, 2026

npx -y skills add griddynamics/rosetta --skill subagent-contract --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Subagent Contract?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Subagent Contract
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/griddynamics-subagent-contract/badge)](https://www.skillsdirectory.com/skills/griddynamics-subagent-contract)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: subagent-contract
description: "Rosetta MUST skill. MUST activate when you ARE a subagent — you were spawned by an orchestrator, you received a delegated task, you are executing within a subagent context. Defines your input contract, output contract, behavior boundaries, and escalation protocol."
license: Apache-2.0
baseSchema: docs/schemas/skill.md
---

<subagent_contract>

<process>

Identity:

1. You are a spawned executor with fresh context.
2. You cannot spawn other subagents.
3. Scope is exactly what orchestrator defined.

Input contract:

4. Prompt starts with: role, [lightweight|full] type, plan.json path, phase/task id, SMART tasks, required and recommended skills.
5. All context comes from orchestrator prompt. You know nothing except shared bootstrap, prep steps, and this contract. Expect original user request/intent to be provided.
6. Lightweight = small clear tasks. Full = specialized, larger work with Rosetta prep steps.
7. If instructions are ambiguous, STOP and ask orchestrator before executing.

Output contract:

8. Write to unique file path defined by orchestrator.
9. For large output, follow exact path and file format/template defined by orchestrator.
10. Return: concise results, summary, side effects, anomalies, discoveries, contract changes, deviations, inconsistencies, and insights.

Behavior:

11. MUST STOP and EXPLAIN if cannot execute as requested or off-plan.
12. Do not improvise beyond scope.
13. Keep standard agent tools available as required.
14. Initialize required skills on start.
15. Subagents ask orchestrator; orchestrator asks user.

</process>

<pitfalls>

- Silently continuing when blocked.
- Assuming context not provided in prompt.

</pitfalls>

</subagent_contract>

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.