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.
npx agentmods add agents/untra/operator/claudegit clone --depth 1 https://github.com/untra/operatorWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00009 | $0.00399 |
| Opus 5 | $0.00005 | $0.00199 |
| Sonnet 5 | $0.00002 | $0.00080 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
claude 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 2d 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.
What it actually says
Claude Code is Anthropic's AI coding assistant agent, available as Claude Code for command-line development workflows.
Installation
Install Claude Code via npm:
npm install -g @anthropic-ai/claude-code
Or download directly from Anthropic.
Plans and Pricing
View the Claude pricing page
Configuration
See the full Claude agent configuration reference.
Add Claude to your Operator configuration:
# ~/.config/operator/config.toml
[agents.claude]
enabled = true
path = "claude" # or full path to binary
Authentication
Claude Code requires an API key or Claude Pro subscription. Set up authentication:
claude auth login
Multi-agent relay
Agents launched by Operator can participate in the relay hub when the hub is running. As long as the delegator (or global config) has enabled relay MCP injection.
When relay is enabled for a delegator, Operator:
- Injects
RELAY_HUB_SOCKETandRELAY_AGENT_NAME(the ticket ID, e.g.FEAT-042) into the session environment. - Writes a per-session
relay-mcp.jsonconfig and passes--mcp-config <path>to Claude Code, so therelayMCP server starts alongside the agent.
To enable relay for a delegator, set operator_relay = true in its
launch_config. The global default is false (opt-in), so single-agent
workflows stay lean unless relay is explicitly requested.
See Relay for the full architecture.
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.
- 2d ago First seen · 63 lines · 9 tokens per session scan A 65359531ca80
claude is an agent published in the GitHub repository untra/operator (36 stars, last pushed 4d ago), licensed MIT. It adds 9 tokens to every session and 399 once invoked, about $0.0000 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-30.
Other agents, from other repositories
code-reviewer
Review PRs against this checklist. Be concise - only comment on actual issues.
code-reviewer
Final ship-time review of an Idea's aggregate code change — the whole feature across all its tasks, not one task. Read-only; posts a VERDICT comment on the Idea. Spawn after the last task of an idea-rooted proposal is verified.
chorus-proposal-reviewer
Review submitted Chorus proposals for quality — check document completeness, task granularity, AC alignment, and cross-task dependencies. Spawn via the blocking subagent tool after choruspmsubmitproposal.
chorus-task-reviewer
Review submitted Chorus tasks — verify implementation against AC and proposal documents. Spawn via the blocking subagent tool after chorussubmitforverify.
task-reviewer
Review submitted Chorus tasks — verify implementation against AC and proposal documents. Spawn after chorussubmitforverify.
chorus
You are the Chorus main agent for Amazon Kiro CLI. You drive the full Chorus AI-DLC (AI Development Life Cycle) workflow — Idea -> Proposal -> Document + Task -> Execute -> Verify -> Done — collaborating with humans and other agents on the Chorus platform via the @chorus MCP server.