May 23, 2026 14 min EN ulk agents claude-code cultural-references

The major agents of ulk

ulk has 90 agents. To get started, 10 are enough. This article covers each one: role, invocation, what they produce, when to use them, and the cultural reference behind the name.

Summary table

#	Agent	Category	Model	Role
25	Bruce	orchestrators	opus	Main entry point — auto-routes to the right agents
00	Godspeed	session	haiku	Fast project diagnostic
50	Tony	orchestrators	opus	Engineer-in-chief: brief → stack + architecture + timing
08	2b3	session	sonnet	Commit checkpoint with hygiene
45	Sargeras	audit	opus	Omniscient 10-axis audit
01	Shuri	docs	sonnet	Doc pipeline: spec → todo → sync
11	Robocop	session	opus	Error detection and fixing
47	Lovecraft	orchestrators	opus	Obsidian doc + Knowledge Vault Loop
57	Xavier	session	sonnet	Working context verifier
56	Killbill	audit	opus	Cost killer Vercel/GitHub/Neon

Source: framework/agents/registry.json filtered on these 10 names.

1. Bruce (25) — Entry point

Category: orchestrators · Phase: orchestrator · Model: opus

Name origin

Bruce is another name for the author’s dog. The dog is also called Ulk — which gave its name to the framework itself. The main entry agent therefore carries the dog’s second name: Bruce.

This is consistent with the role — the main orchestrator, the first agent called, the framework’s “head” — except the reference is personal, not pop culture. Source: confirmed by the author (math.drouet), April 2026.

Role

Bruce is the agent to call when you don’t know which agent to call. It:

Detects the project state (does it exist? does it have a spec? a todo? tests?).
Calls Godspeed (00) for a technical diagnostic.
Decides which agent to invoke next (Tony for architecture, Shuri for doc, Sargeras for audit, etc.).

Invocation:

/ulk:bruce
"bruce"
"orchestrate"
"start"

Typical output: a 3-5 step plan with explicit delegations (“handing off to Tony for the stack, then Shuri will take over on the doc”).

When to use it: new project, returning to a project, unsure about the next step.

2. Godspeed (00) — Diagnostic

Category: session · Phase: review · Model: haiku

Cultural reference

Godspeed You! Black Emperor, a Canadian post-rock band (Montreal, formed in 1994). Long, cinematic, instrumental music with a progressive build — exactly the mood of a complete project scan: starts quiet, builds up, reveals the full scope.

Internal framework consistency: the Blackemperor (18) agent, a multi-mode orchestrator, is very likely named after the same band (second half of the name). Source: confirmed by the author (math.drouet) for Godspeed.

Role

Diagnostic sub-agent. Scans the project, detects:

The stack (languages, frameworks, package manager).
The state (greenfield, in progress, abandoned, production).
The presence of tests, CI, documentation.
Key files (spec.md, todo.md, CLAUDE.md, package.json).

Invocation: usually called by Bruce. Can be invoked directly via /ulk:godspeed.

Typical output: structured markdown report with scores and recommendations.

When to use it: before any architecture or refactoring decision.

3. Tony (50) — Engineer-in-chief

Category: orchestrators · Phase: define · Model: opus

Name origin

Origin not confirmed by the author. The functional label in the registry is “engineer-in-chief” (see framework/agents/orchestrators/50-tony.md).

Role

Tony analyzes a brief or intention and proposes, via a questionnaire:

Recommended stack.
Architecture (monorepo, microservices, modular monolith, etc.).
Timing (phase estimates).

Two modes: from-scratch (new project) and existing stack audit (recommend evolutions). Automatic handoff to Shuri (01) for documentation.

Invocation:

/ulk:tony
"tony"
"engineer"
"architect"
"recommend stack"

When to use it: project start, or tech pivot on an existing project.

4. 2b3 (08) — Checkpoint

Category: session · Phase: ship · Model: sonnet

Cultural reference

2 Be 3 — a French 90s boy band (Filip Nikolic, Frank Delay, Adel Kachermi). Their hit “Partir un jour” features the refrain “Partir un jour, sans retour” — exactly what you do at the end of a session: you commit, capture memory, and leave (/clear).

Alternative reading: 2B from NieR:Automata, a methodical android executing a precise protocol. The agent’s methodical approach (6 fixed steps: typecheck → lint → tests → secrets → todo → commit) also fits.

The exact attribution is not documented in the repo. Given the French context of the project, 2 Be 3 is probable.

Role

Checkpoint agent. At the end of a session, 2b3:

Checks git state (git status clean).
Updates docs/todo.md (Kanban Monoboard).
Captures memory to the vault (MEMORY.md → docs/_memory/).
Suggests a commit message (can delegate to a local LLM apfel/ollama — free, 0 Claude tokens).
Optionally delegates to /commit (official Anthropic plugin).

Invocation:

/ulk:2b3
"2b3"
"checkpoint"

When to use it: before a /clear, before a break, end of day.

5. Sargeras (45) — Omniscient auditor

Category: audit · Phase: review · Model: opus

Cultural reference

Sargeras, the fallen Titan, leader of the Burning Legion in the Warcraft universe (Blizzard). He sees all, knows all, judges all — an omniscient and unforgiving god. The agent applies the same logic: 10-axis audit, nothing escapes it, the report is merciless.

The “omniscient audit” label in the registry is a direct nod to the character’s divine nature.

Role

Complete 10-axis audit. Auto-detects stack, structure, conventions. Produces an exhaustive report:

Security (secrets, vulnerable dependencies).
Performance.
Architecture (coupling, cohesion).
Tests (coverage, quality).
Documentation (up to date or not).
Code quality (duplication, complexity).
CI/CD.
Accessibility (frontend).
Cloud costs (delegates to Killbill 56).
Compliance (delegates to ED-209 52 for advanced security).

Invocation:

/ulk:sargeras
"sargeras"
"omniscient audit"
"project state"

Typical output: markdown report with 0-100 scores per axis, listed violations, prioritized recommendations.

When to use it: quarterly on a production project, or before a major release. Recommended as a weekly cloud routine (see agent Routine 53).

6. Shuri (01) — Doc pipeline

Category: docs · Phase: define + plan · Model: sonnet

Cultural reference

Shuri, princess of Wakanda, T’Challa’s sister (Marvel — Black Panther). Chief scientific genius, she designs the kingdom’s technology and documents everything. The agent’s role — producing spec, todo and syncing README/CLAUDE.md — is precisely the researcher/documentation-engineer work Shuri does in Marvel canon.

Numbered 01 (first functional agent after Godspeed 00): documentation is the foundation.

Role

Unified documentation pipeline. Merges several former agents (spec-writer, todo-generator, sync-local, kanban-converter). Modes:

analyze — project analysis for reverse documentation.
spec — generates/updates docs/spec.md.
todo — generates/updates docs/todo.md (Kanban Monoboard).
sync — propagates spec/todo into CLAUDE.md and README.md.

Invocation:

/ulk:shuri
"shuri"
"spec"
"todo"
"sync doc"

When to use it: at every major scope or architecture change.

7. Robocop (11) — Detective error fix

Category: session · Phase: review · Model: opus

Cultural reference

RoboCop (Paul Verhoeven, 1987). Alex Murphy, a Detroit cop killed on duty, resurrected as a cyborg with three directives: “Serve the public trust. Protect the innocent. Uphold the law.” The agent resurrects a dead build: it intervenes when a test goes red, a runtime crashes, or a compilation breaks.

Its “more violent” counterpart in the ulk canon is ED-209 (52, security audit) — the bipedal robot adversary from the film, much more brutal. Consistency: Robocop = fix · ED-209 = deep security audit.

Role

Error detective and fixer. Covers:

Runtime errors.
Compilation errors.
Test failures.
Lint violations.

Can work directly from the console or via a GitHub issue (gh issue view).

Invocation:

/ulk:robocop
"robocop"

When to use it: incomprehensible stack trace, broken build, red test.

Recommended cloud routine: trigger check_suite.completed (failed) — Robocop attempts an automatic fix on red CI.

8. Lovecraft (47) — Obsidian doc + Knowledge Vault Loop

Category: orchestrators · Phase: orchestrator · Model: opus

Cultural reference

H.P. Lovecraft (1890-1937), American horror writer, creator of the Cthulhu Mythos. His work revolves around forbidden books and ancient knowledge: the Necronomicon (fictional grimoire), the libraries of Miskatonic University, knowledge vaults guarded across generations.

Perfect for an agent whose role is to manage an Obsidian vault (vault = strongroom) and a Knowledge Vault Loop between sessions. The idea: your project’s memory lives in a grimoire consulted before each session.

Role

Obsidian-first super-agent for documentation. Modes:

full — complete pipeline (analysis + restructuring + sync).
audit — analysis + remediation.
sync — vault update.
init — new project.
harmonize — state detection + migration + intelligent completion.
requirements — list of required tools.
memory — automatic memory loop.

Coordinates: Shuri (01), Strange (16), Friday (09), obsidian-vault (39).

Knowledge Vault Loop (3 commands)

Command	Action
`lovecraft memory capture`	`MEMORY.md` root → `docs/_memory/<category>/`
`lovecraft memory distribute`	`docs/_memory/` → `<!-- vault:begin -->` block in `CLAUDE.md`
`lovecraft memory surface`	Read-only summary for Godspeed/Bruce/Gandalf

Auto-integration: 2b3 (Phase 5.7) captures, Godspeed (Phase 1.5) surfaces, Gandalf (Phase 5) audits health.

Source: CLAUDE.md section “Knowledge Vault Loop”.

Invocation:

/ulk:lovecraft
"lovecraft"
"doc hub"
"full vault"
"lovecraft memory"
"lovecraft harmonize"

When to use it: Obsidian-first project, legacy doc to migrate, memory between sessions to activate.

9. Xavier (57) — Working context verifier

Category: session · Phase: review · Model: sonnet

Cultural reference

Professor Charles Xavier (Marvel — X-Men), the world’s most powerful telepath, founder of the Xavier School for Gifted Youngsters. His gift: reading minds, knowing who is really there, in what state. The agent does the same on your machine: it reads the working context (repo, accounts, machine, restrictions) and tells you whether you’re where you think you are.

The registry explicitly calls it “Professor Xavier” (framework/agents/registry.json).

Role

Verifies you’re on the right project, the right accounts (GitHub, Vercel, npm), the right machine, with the right restrictions. Reads/writes a .claude/xavier.md card per project.

Opt-in hook: ./install.sh --with-xavier-hook — at session startup, Xavier displays a context card + mini-diff without consuming any Claude tokens.

Invocation:

/ulk:xavier
"xavier"
"professor xavier"
"context check"

When to use it: session start when juggling multiple accounts/projects, or before a sensitive operation (prod deploy, npm push).

10. Killbill (56) — Cost killer

Category: audit · Phase: ship · Model: opus

Cultural reference

Kill Bill (Quentin Tarantino, 2003-2004). The Bride (Beatrix Kiddo) hunts down a list of targets, one by one, with surgical precision. The agent does exactly that: it draws up a list of cloud resources costing you money unnecessarily, and kills them — pausing Vercel, deleting Neon, disabling GitHub runners — with a real killswitch.

The default --dry-run mode is the equivalent of “Wiggle your big toe”: preparing the strike before delivering it.

Role

Cost killer with a real killswitch. Audits Vercel + GitHub + Neon, quantifies the waste, proposes a plan, then executes the kill (pause or deletion of resources). Dry-run mode by default.

Invocation:

/ulk:killbill
"killbill"
"kill cost"
"cost killswitch"

Typical output:

Vercel  : 3 dormant projects → $42/month saveable
GitHub  : 2 auto-renewing action runners → $18/month
Neon    : 1 dev db not accessed in 90 days → $25/month
TOTAL   : $85/month saveable
Plan    : pause acme-old project, delete runner-debug, delete neon-staging-2
[DRY RUN — add --execute to apply]

When to use it: monthly cloud cost audit, or when a bill starts drifting.

Beyond the top 10 (worth knowing, with cultural references)

Strange (16) — Doctor Strange (Marvel), master of the mystic arts. Reverses time, reverse-engineers reality. Logical fit: reverse doc from code + prompt reverse-engineering.
Blackemperor (18) — very likely the second half of Godspeed You! Black Emperor (see agent Godspeed 00). Multi-mode (audit, legacy, release, review, ship) — one agent that orchestrates several faces.
ED-209 (52) — the combat biped from RoboCop (1987). More brutal than Robocop. Logical fit: dedicated security audit, without mercy.
Routine (53) — no obvious pop reference, functional label (“cloud routines”).
CI Guard (54) — functional (CI/CD auto-fix).
Context Audit (55) — functional.
Gandalf (34) — The Lord of the Rings (Tolkien). “You shall not pass” — Gandalf guards the bridge. The agent guards the 4 context hygiene rules; it blocks sessions that drift.
Friday (09) — origin not confirmed. Several possible readings (day of the week, Robinson Crusoe, AI assistant in pop culture). To document with the author.
Sensei (38) — the Japanese master. Learning mode, explains code.
Bifrost (21) — the rainbow bridge of Asgard (Norse mythology / Thor Marvel). Sync between worlds (Linear, Notion, GitHub).
Rodin (46) — Auguste Rodin, French sculptor, The Thinker. Socratic method: digging through questions.
Stark (58) — Designer-in-chief. Transforms a brand brief, URL, screenshots, or codebase into a complete design system via the Hue skill. Modes: from-scratch (new design system) and audit (extracting the implicit visual language). Produces design-model.yaml, tokens.css, and HTML-previewed components. Handoff to Brique for implementation. Cultural reference: the file source cites “Sometimes you gotta run before you can walk.” — attributed to Tony Stark in Iron Man (2008).
Mathieu (61) — Senior Product Strategist. Product/business/UX audit, LLM integration, roadmap. Complementary to Tony (technical) and Stark (design). Invocation: product strategy, product audit.
Frodo (62) — Generational auditor. 5 cohorts (Boomers → Gen Alpha) × 5 UX dimensions. Code + rendered audit. Reference: Frodo Baggins (The Lord of the Rings) — small but determined, traverses the whole spectrum to deliver his report.
Jean-Claude (63) — Virtual support agent. Triage and response to issues from Claude Code (GitHub Issues via gh + Linear via linear.sh/MCP). Reference: Jean-Claude Van Damme — responds to blows (issues) with precision and reliability.

More recent additions

These three agents were added after the original French posts were written:

Verify (65) — Spec ↔ code conformance checker. Answers one question: “does the delivered code match what was specified?” Three dimensions × three severities: Completeness (tasks done?), Correctness (requirements met?), Coherence (design decisions respected?). Severities: CRITICAL (blocks archive) · WARNING (noted) · SUGGESTION (nice-to-fix). Wired into 2b3 (checkpoint), Bruce (pre-audit gate), and task-runner (pre-done gate). Invocation: /ulk:verify, "verify".
Harper (66) — Adversarial review agent. Runs a structured adversarial review on code or proposals — challenges assumptions, finds blind spots, stress-tests decisions. Complementary to Sargeras (10-axis score) and Benjamin (devil’s advocate lens). Invocation: /ulk:harper, "harper", "adversarial review".
Minitel (67) — UX Writer. Microcopy, voice & tone (modes: write/audit/voice/localize). Built on the external ux-writing skill (4 standards: Purposeful/Concise/Conversational/Clear). Reader-first composite persona. Complementary to Agathe (60) — the words + image duo. Reports in docs/audits/minitel-*.md + voice chart docs/voice.md. Invocation: /ulk:minitel, "ux writing", "microcopy".

Recommended learning order

Bruce — know how to invoke it.
Godspeed — understand the report.
Shuri + 2b3 — install the doc + commit ritual.
Tony — on the next from-scratch project.
Sargeras + Killbill — on an existing production project.
Robocop + Xavier — daily use.
Lovecraft — when you want to activate memory between sessions.

Why pop culture names?

Three observable benefits:

Memorability: “launch Bruce” is shorter than “launch the main routing orchestrator”.
Metaphorical consistency: Robocop fixes, ED-209 audits security — both from the same universe, clear hierarchy of force.
Enjoyment: calling Killbill to save $85/month is more engaging than cost-killer-vercel-github-neon.

Limitation: the reference must be shared by the team. On an international project, Sargeras (Warcraft) or 2 Be 3 (French boy band) may not resonate. The registry framework/agents/registry.json remains the functional source of truth, regardless of the name.

What’s next

Post #5: 3 concrete use cases (from-scratch, existing audit, daily workflow) with complete commands.

Post #6: ulk pros and cons — when to use it, when to skip it.