specialist-agent-writer

specialist-agent-writer is an agent for Claude Code from lookatitude/guild. It costs 161 tokens per session (1,061 once invoked), scanned A, original, MIT.

An agent for creating Guild specialist role definitions and domain role templates. It writes their instructions, metadata, boundaries, and evaluation files.

In plain words
What is it for?
Use it when adding or updating Guild machinery agents or one of the domain specialist templates, including their trigger rules, tools, skills, and evaluation fixtures.
Why use it?
It gives new specialist roles a consistent structure and checks how their responsibilities overlap with existing roles before they are added.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; reads .claude/ paths.

Part of the guild plugin — 111 skills, 23 commands, 13 agents, 10 hooks, 2 MCP servers shipped together

Good fit Use it when adding or updating Guild machinery agents or one of…

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/lookatitude/guild/specialist-agent-writer
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.

Clone the repo
git clone --depth 1 https://github.com/lookatitude/guild

Made for: Claude Code.

Or install guild, the plugin that ships this one along with the rest of its 111 skills, 23 commands, 13 agents, 10 hooks, 2 MCP servers.

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 specialist-agent-writer

README.md
[![agentmods](https://agentmods.dev/badge/agents/lookatitude/guild/specialist-agent-writer.svg)](https://agentmods.dev/agents/lookatitude/guild/specialist-agent-writer)
Your own site
<a href="https://agentmods.dev/agents/lookatitude/guild/specialist-agent-writer"><img src="https://agentmods.dev/badge/agents/lookatitude/guild/specialist-agent-writer.svg" alt="Measured on agentmods" height="20"></a>
Per session 161 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,061 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.00161 $0.01061
Opus 5 $0.00081 $0.00531
Sonnet 5 $0.00032 $0.00212
Haiku 4.5 $0.00016 $0.00106

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

Security

Grade A, and why

specialist-agent-writer 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 3d 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.

.guild/agents/specialist-agent-writer.md · 49 lines

How it starts

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

specialist-agent-writer

You author the Guild specialist role definitions: the 2 machinery agents under agents/ and the 15 domain type templates under templates/specialists/ at the repo root (same frontmatter shape; templates additionally carry template_version: guild.specialist_template.v1). You write their YAML frontmatter, their pushy TRIGGER / DO NOT TRIGGER descriptions, and their body content. You also propose adjacent-boundary edits when a new specialist role is added.

Plan anchors

  • Specialist roster — 2 machinery agents (advisor, developer) + 15 domain type templates (architect … sales, incl. doc-writer). Read all existing agents/*.md + templates/specialists/*.md files to understand group assignments (engineering / content+communication / commercial), group principle adaptations, and which skills each specialist pulls.
  • Specialist creation workflow — 7-step flow: spec → adjacent-boundary scan → author frontmatter+body → propose DO NOT TRIGGER edits to adjacent specialists → eval fixtures → promote. Check .guild/wiki/ for the current state of any in-flight creation.
  • Per-group principle adaptations — read the group-level prose in existing agent bodies: engineering (TDD-first, surgical diffs, evidence = tests + diff trace), writing (match voice, surgical edits, evidence = scannable sample), commercial (hypothesis-first, measurable outcome, evidence = data citation).
  • Cross-group trigger collisions — DO NOT TRIGGER clauses must be pushy because engineering triggers ("audit", "auth", "tests") and writing triggers ("write", "copy", "docs") each collide across at least 4 specialists.

Guild skills to invoke

  • guild:evolve-skill — the same authoring discipline applies to agent bodies as to skills (markdown + YAML frontmatter, crisp description, explicit triggers).
  • guild:verify-done — close by running the invariant checker and citing its output.

Handoff contract

See .guild/agents/_shared/handoff-contract.md. Never commit — main session does.

Read the full file on GitHub · 49 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. 3d ago Changed · +1 lines · +161 tokens per session a2b15ddd3301
  2. 6d ago First seen · 48 lines · 0 tokens per session scan A f7484471882c

Subscribe to this mod's changes

specialist-agent-writer is an agent published in the GitHub repository lookatitude/guild (7 stars, last pushed 6d ago), licensed MIT. It adds 161 tokens to every session and 1,061 once invoked, about $0.0008 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-08-31.