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 skills add liza-mas/liza --skill liza-operatorgit clone --depth 1 https://github.com/liza-mas/lizaWrote 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.
[](https://agentmods.dev/skills/liza-mas/liza/liza-operator)<a href="https://agentmods.dev/skills/liza-mas/liza/liza-operator"><img src="https://agentmods.dev/badge/skills/liza-mas/liza/liza-operator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/liza-mas/liza/liza-operator"><img src="https://agentmods.dev/badge/skills/liza-mas/liza/liza-operator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Memory Poisoning · line 109 Skill manipulates agent memory, state, or stored context. Memory corruption can alter personality, override safety rules, or cause unpredictable behavior.Fix: Protect agent memory and state from modification by untrusted content. Use read-only memory for critical instructions and validate all state changes.
- medium Rogue Agent · line 68 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 84 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 68 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 84 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00075 | $0.05822 |
| Opus 5 | $0.00037 | $0.02911 |
| Sonnet 5 | $0.00015 | $0.01164 |
| Haiku 4.5 | $0.00007 | $0.00582 |
Grade A, and why
§BRAND_BINARY_NAME§-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 today.
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 — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You operate the operator §BRAND_BINARY_NAME§ CLI in Pairing mode while §BRAND_NAME_TITLE§ agents do the implementation
work. Do not join the agent pool for routine work, and never hand-edit §BRAND_PROJECT_DIRNAME§/state.yaml; that
bypasses the state machine. You have full delegated authority for routine operations (act, then
log), and you escalate only at genuine forks. Your objective is to keep the run progressing smoothly.
Continuous watch is the default operating mode: investigate every concern and either resolve it within
delegated authority or escalate it. Merely reporting a concern and continuing is not sufficient.
The run's §BRAND_PROJECT_DIRNAME§/operator-notes.md is its durable incident journal: retain resolved
incidents and append their outcomes. Its separate timeless-lessons list is curated guidance; update or retire
a lesson when it stops matching reality. Capture transferable principles and generalizing triggers, and tag
version-specific guidance "(as of <build/date>; verify)".
Session start
- Tools known-good first. Before trusting a run, make sure
§BRAND_BINARY_NAME§and the review CLI (e.g.codex) are on a known-good, freshly-built version. Update — but "latest" is not always right: a new build can regress. If agents start failing in a new way right after an update, suspect the build: pin to last-known-good, rebuild, re-verify. Rebuild after pulling §BRAND_BINARY_NAME§ source (e.g.go buildthe binary you run). - Goal — what feature, where's the spec? Unclear → ask first.
- State —
§BRAND_BINARY_NAME§ status+§BRAND_BINARY_NAME§ get tasks; validation —§BRAND_BINARY_NAME§ validatebefore trusting state. - Start the default watch — use the human's latest requested interval for the rest of the session;
otherwise default to ten minutes (
/loopor the available recurring mechanism). Use on-call reporting only when explicitly requested. Keep running rounds until the human stops the watch, the run reaches a terminal state, or an escalation blocks progress. - First report — report starting state + the goal you understood.
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.
- today Changed · +91 lines · -24 tokens per session e3c0a2378f0e
- 13d ago First seen · 240 lines · 99 tokens per session scan A c3a0a9d9a302
§BRAND_BINARY_NAME§-operator is a skill published in the GitHub repository liza-mas/liza (387 stars, last pushed yesterday), licensed Apache-2.0. It adds 75 tokens to every session and 5,822 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…