# Agents (https://docs.neuralisapp.com/package-system/agents)

An `agents/*.md` file defines a persona the platform's `delegate` tool can
spawn as a sub-agent. The file body becomes the child agent's system prompt;
frontmatter `name`, `allowed-tools`, and `model` are honored when the run is
created.

```markdown
---
name: reviewer
description: Reviews a change set against the project conventions.
allowed-tools: [fs_read, fs_search]
---

You are a meticulous code reviewer. Inspect the files you are pointed at...
```

## Tool ceiling [#tool-ceiling]

- Omitting `allowed-tools` inherits the caller's own tool set.
- An explicitly empty `allowed-tools: []` is honored: the child runs with no
  tools.
- On a persona the list is a **ceiling**: a `delegate` call naming its own
  `tools` is intersected with it and can only narrow, the dropped names are
  reported back in the result, and a call asking for none of them is refused.

## Resolution [#resolution]

The delegate tool resolves a requested agent by id or name from the
first-class agent array, falling back to skill-forks — skills whose frontmatter
declares `context: fork` register in the agent category and resolve the same
way (see [Skills](https://docs.neuralisapp.com/package-system/skills.md)).

## Identity [#identity]

The child run inherits the parent's package enablement and the caller's real
identity and grants — a delegate never escalates beyond what the calling user
could do. Personas obey the same visibility gates as every category
([Instructions → Visibility](https://docs.neuralisapp.com/package-system/instructions.md#visibility)).

A persona is a spawn-time identity. A long-lived coworker with its own
identity files and settings is a [team member](https://docs.neuralisapp.com/package-system/team.md).
