agent-archetypes

agent-archetypes is a skill for Claude Code, Codex from mattmre/EVOKORE-MCP-PUBLIC. It costs 16 tokens per session (2,735 once invoked), scanned A, original, MIT.

A set of reference definitions for common roles in a multi-agent software system. It describes what orchestrators, planners, code workers, quality checks, researchers, and browser agents are responsible for.

In plain words
What is it for?
Use it when designing a team of agents and assigning responsibilities, inputs, outputs, permissions, and operational limits.
Why use it?
It gives each agent a clear role, scope, and escalation path, reducing overlap and confusion in a coordinated workflow.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when designing a team of agents and assigning responsibilities, inputs, outputs, permissions, and operational limits.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mattmre/evokore-mcp-public/agent-archetypes
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add mattmre/EVOKORE-MCP-PUBLIC --skill agent-archetypes
Clone the repo
git clone --depth 1 https://github.com/mattmre/EVOKORE-MCP-PUBLIC

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for agent-archetypes

README.md
[![agentmods](https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/agent-archetypes/github.svg)](https://agentmods.dev/skills/mattmre/evokore-mcp-public/agent-archetypes)
Your own site
<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/agent-archetypes"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/agent-archetypes/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.

agentmods 80×15 button for agent-archetypes

Your own site · 80×15
<a href="https://agentmods.dev/skills/mattmre/evokore-mcp-public/agent-archetypes"><img src="https://agentmods.dev/badge/skills/mattmre/evokore-mcp-public/agent-archetypes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,735 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00016 $0.02735
Opus 5 $0.00008 $0.01367
Sonnet 5 $0.00003 $0.00547
Haiku 4.5 $0.00002 $0.00274

Measured 8d ago against content hash d927897f99da, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

agent-archetypes 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 8d 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.

SKILLS/ORCHESTRATION FRAMEWORK/agent-archetypes/SKILL.md · 218 lines

How it starts

The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Archetypes

Reference architecture for multi-agent orchestration systems. These six agent definitions, imported from Agent33, establish the core roles, governance boundaries, and capability assignments needed to run a structured agent pipeline.

Each agent is defined as a JSON file that declares its role, inputs/outputs, governance scope, capability set, and operational constraints. Together they form a composable team where the orchestrator decomposes work, the director plans strategy, workers execute, QA validates, the researcher gathers information, and the browser agent handles web interaction.

Agent Summary

Agent ID Role Scope Key Capabilities Escalation Target
Orchestrator AGT-001 orchestrator full-system P-01, P-02, P-03, P-05, V-05 human-operator
Director AGT-002 director project-level P-01, P-02, P-03, P-04, P-05 orchestrator
Code Worker AGT-003 worker assigned-workspace I-01, I-02, I-03, I-04, I-05 orchestrator
QA AGT-004 qa test-workspace V-01, V-02, V-03 orchestrator
Researcher AGT-006 researcher read-only X-01, X-02, X-03, X-04, X-05 orchestrator
Browser Agent -- worker browser-sandbox (none assigned) orchestrator

Agent Traits and Constraints

  • Orchestrator -- No dependencies; top of the chain. Has full-system command access and internal-only network. No parallel execution. 8192 token limit, 300s timeout, 3 retries.
  • Director -- Reports to orchestrator. No direct command execution; plans only. Requires approval for scope changes. 8192 token limit, 240s timeout, 2 retries.
  • Code Worker -- Reports to orchestrator. Scoped to assigned workspace with build/test/lint commands. Requires approval for deploy. Parallel execution allowed. 16384 token limit, 180s timeout.
  • QA -- Reports to orchestrator. Scoped to test workspace with test/lint/check commands. Parallel execution allowed. 8192 token limit, 180s timeout.
  • Researcher -- Optionally reports to orchestrator. Read-only scope with external-read network access. No parallel execution. 32768 token limit, 300s timeout.
  • Browser Agent -- Optionally reports to orchestrator. Sandboxed browser scope with external-read network. Parallel execution allowed. 16384 token limit, 300s timeout.

Read the full file on GitHub · 218 lines

Changes

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.

  1. 8d ago First seen · 218 lines · 16 tokens per session scan A d927897f99da

Subscribe to this mod's changes

agent-archetypes is a skill published in the GitHub repository mattmre/EVOKORE-MCP-PUBLIC (3 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 2,735 once invoked, about $0.0001 per session on Opus 5. 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-03.

Related

Other skills, from other repositories

law-of-similarity

Apply the Law of Similarity — shared colour, shape, or size signals that elements belong to one category. Use when signalling relationships across distance. For grouping by position, use law-of-proximity.

Owl-Listener/designer-skills · 47 tokens

law-of-common-region

Apply the Law of Common Region — a shared container, background, or border groups elements regardless of spacing. Use when grouping must survive a tight layout. For grouping by spacing alone, use law-of-proximity.

Owl-Listener/designer-skills · 48 tokens

critique-visual-hierarchy

Critique a rendered screen's hierarchy — entry point, eye flow, weight distribution, and emphasis. Use when attention lands in the wrong place. For establishing hierarchy in new work, use visual-hierarchy (ui-design).

Owl-Listener/designer-skills · 53 tokens

version-control-strategy

Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use design-system-governance (design-systems).

Owl-Listener/designer-skills · 50 tokens

presentation-deck

Structure a design presentation for a specific audience and decision. Use when presenting internally. For a portfolio narrative use case-study; for the written argument use design-rationale.

Owl-Listener/designer-skills · 39 tokens

accessibility-test-plan

Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use accessibility-audit (design-systems).

Owl-Listener/designer-skills · 52 tokens