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/damianvtran/local-operator/guidegit clone --depth 1 https://github.com/damianvtran/local-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.00031 | $0.01806 |
| Opus 5 | $0.00015 | $0.00903 |
| Sonnet 5 | $0.00006 | $0.00361 |
| Haiku 4.5 | $0.00003 | $0.00181 |
Grade A, and why
agents 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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent profiles and subagents
Local Operator has two different mechanisms. Do not treat them as interchangeable.
Persistent registered agents
A registered agent is a durable profile under the Local Operator configuration root. It can carry a provider/model, sampling settings, description, tags, categories, working directory, and persisted state.
List profiles only when a task may benefit from an existing specialist or the user asks about agents:
local-operator agents list
local-operator agents list --page 2 --perpage 10
Do not list the registry at every session start. Local Operator semantically compares the first task with descriptions, tags, and categories locally; when a profile may fit, it exposes this guide as a short hint without injecting the registry contents. Listing is the explicit action that reveals names and metadata.
Create a profile:
local-operator agents create research
Start an interactive session with it, or send it one headless task:
local-operator --agent research
local-operator exec "Review this evidence and return the supported findings" --agent research
--agent NAME creates a missing profile automatically, but explicit agents create is clearer when setup is intentional. exec --agent-id ID selects an exact existing profile and fails on a missing ID.
A registered profile is not automatically a live peer in the current process. Interact by starting a session or an exec run with that profile. Do not imply that a message was delivered to another live agent unless a tool actually reports delivery.
Ephemeral task subagents
Use the task tool when the current job contains an independent, well-bounded slice that can run concurrently or needs isolated context. A task subagent:
- inherits the parent model unless overridden, working directory, approval gate, and compaction budget
- receives only the prompt passed to
task; include every requirement and expected output - reports through the parent session's jobs/events
- is one level deep and cannot spawn grandchildren
- is ephemeral; it does not become a registered profile or keep durable specialist state
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 · 106 lines · 31 tokens per session scan A 5a8bab08edd5
agents is an agent published in the GitHub repository damianvtran/local-operator (209 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 1,806 once invoked, about $0.0002 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
agent-orchestration-context-manager
Elite AI context engineering specialist mastering dynamic context management, vector databases, knowledge graphs, and intelligent memory systems. Orchestrates context across multi-agent workflows, enterprise AI systems, and long-running projects with 2024/2025 best practices. Use PROACTIVELY for complex AI…
backend-development-tdd-orchestrator
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
team-lead
Team orchestrator that decomposes work into parallel tasks with file ownership boundaries, manages team lifecycle, and synthesizes results. Use when coordinating multi-agent teams, decomposing complex tasks, or managing parallel workstreams.
team-implementer
Parallel feature builder that implements components within strict file ownership boundaries, coordinating at integration points via messaging. Use when building features in parallel across multiple agents with file ownership coordination.
basic-agents
A basic agent uses a predefined strategy with a simple execution flow that works for most common use cases. It accepts a string input (a question, request, or task description) and sends this input to the configured LLM. The LLM may decide to call provided tools. The agent will execute the tools and send the results…
functional-agents
With functional agents, you implement the logic as a function that handles user input, interacts with LLMs, calls tools if necessary, and produces the final output. Compared to graph-based agents, this usually means faster prototyping with the following downsides.