multi-agent-example

A complete example of several AI agents working together, with separate agents researching, writing, editing, and publishing a business article.

In plain words
What is it for?
Use it as a reference for building workflows where specialist agents pass work between one another and publication waits for human approval.
Why use it?
It gives developers a runnable workflow to study and adapt instead of designing multi-agent coordination from the beginning. It also shows automated checks and a required human approval step.

Plugin for Claude Code

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.

Claude Code
/plugin marketplace add jamesgray-ai/handsonai-plugins
agentmods
npx agentmods add plugins/jamesgray-ai/handsonai-plugins/multi-agent-example
Clone the repo
git clone --depth 1 https://github.com/jamesgray-ai/handsonai-plugins

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

multi-agent-example 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.

plugins/multi-agent-example/.claude-plugin/plugin.json · 19 lines

What it actually says

{
  "name": "multi-agent-example",
  "description": "A complete, runnable worked example of multi-agent orchestration. Four specialist agents research, write, edit, and publish a business article, with automatic delegation, machine quality gates, and an enforced human approval step. Built to be read and adapted, not used as-is.",
  "version": "1.0.2",
  "author": {
    "name": "James Gray"
  },
  "homepage": "https://handsonai.info/ai-workflow-framework/examples/autonomous-agent/",
  "license": "MIT",
  "keywords": [
    "worked-example",
    "multi-agent",
    "subagents",
    "orchestration",
    "hooks",
    "human-in-the-loop"
  ]
}
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. yesterday First seen · 19 lines scan A d010f171dda2

Subscribe to this mod's changes

multi-agent-example is a plugin published in the GitHub repository jamesgray-ai/handsonai-plugins (8 stars, last pushed 20d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-08-31.