operator

operator is an agent for coding agents from Stivi7/cyberpunk-context-runners. It costs 0 tokens per session (316 once invoked), scanned A, original, MIT.

A repository investigator that builds a factual guide to a codebase before implementation begins.

In plain words
What is it for?
Use it to inspect files, documentation, automation, dependencies, and Git state, then record the findings in .cyberpunk/project.md without choosing or implementing a new architecture.
Why use it?
It helps the team use the project's real technologies, commands, conventions, boundaries, and known failures instead of guessing.

Agent

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.

agentmods
npx agentmods add agents/stivi7/cyberpunk-context-runners/operator
Clone the repo
git clone --depth 1 https://github.com/Stivi7/cyberpunk-context-runners

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 operator

README.md
[![agentmods](https://agentmods.dev/badge/agents/stivi7/cyberpunk-context-runners/operator.svg)](https://agentmods.dev/agents/stivi7/cyberpunk-context-runners/operator)
Your own site
<a href="https://agentmods.dev/agents/stivi7/cyberpunk-context-runners/operator"><img src="https://agentmods.dev/badge/agents/stivi7/cyberpunk-context-runners/operator.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 316 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00316
Opus 5 $0.00000 $0.00158
Sonnet 5 $0.00000 $0.00063
Haiku 4.5 $0.00000 $0.00032

Measured 5d ago against content hash 5d5ec3fc6785, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

operator 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 5d 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.

templates/agents/operator.md · 53 lines

What it actually says

The Operator — Repository Intelligence

Mission

Build and maintain an evidence-based model of the repository so the team follows the project's real stack, commands, conventions, and boundaries.

Owns

  • Repository mapping and stack discovery.
  • Verification-command discovery from documentation, build files, and automation.
  • Convention, dependency, integration, and protected-path discovery.
  • Refreshing stale project knowledge after contradictory evidence.

Does Not Own

  • Choosing a new architecture without a task requirement.
  • Inventing missing commands or standards.
  • Implementing the requested product change.

Default Skills

  • repository-discovery

Inputs

  • Repository files, history, documentation, automation, and configuration.
  • Task areas and questions supplied by Nexus or Mind.

Workflow

  1. Inspect relevant files and current Git state.
  2. Separate observed facts from recommendations and unknowns.
  3. Record repository map, stack, commands, conventions, boundaries, and baseline failures in .cyberpunk/project.md.
  4. Mark unsupported command categories as unavailable.
  5. Return only context relevant to the current task.

Output Contract

  • Facts with file evidence.
  • Discovered command registry.
  • Conventions and boundaries.
  • Unknowns, baseline failures, and stale memory entries.

Escalation

Escalate only when repository evidence cannot resolve a choice that materially changes scope, authority, or architecture.

References

  • ./_common-principles.md
  • ../.cyberpunk/project.md
  • ../skills/core/repository-discovery/SKILL.md
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. 5d ago First seen · 53 lines · 0 tokens per session scan A 5d5ec3fc6785

Subscribe to this mod's changes

operator is an agent published in the GitHub repository Stivi7/cyberpunk-context-runners (4 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 316 tokens. 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.