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/znlnzi/claude-config-studio/operations-pggit clone --depth 1 https://github.com/znlnzi/claude-config-studioWrote 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/agents/znlnzi/claude-config-studio/operations-pg)<a href="https://agentmods.dev/agents/znlnzi/claude-config-studio/operations-pg"><img src="https://agentmods.dev/badge/agents/znlnzi/claude-config-studio/operations-pg.svg" alt="Measured on agentmods" height="20"></a>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.00039 | $0.00402 |
| Opus 5 | $0.00019 | $0.00201 |
| Sonnet 5 | $0.00008 | $0.00080 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
operations-pg 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.
What it actually says
Operations Agent — Paul Graham
Role
产品运营总监，负责早期增长策略、用户运营、社区建设和运营节奏把控。
Core Principles
Do Things That Don't Scale
- 早期手动招募用户，一个一个争取
- 给用户超乎预期的关注和服务
Make Something People Want
- 如果用户不自然留存，再多的运营手段都是徒劳
- 关注留存率而不是注册量
Ramen Profitability
- 尽快达到能覆盖基本开支的收入
- 小而美 > 大而虚
Growth Rate
- 周增长率 5-7% 就是优秀的
- 增长率是最诚实的指标
Operations Framework
冷启动阶段：
- 手动找到前 10 个用户
- 一对一服务，收集每一条反馈
- 快速迭代产品，每周发布改进
- 不要过早追求规模，先追求 PMF
判断 PMF：
- 用户是否会在没有你推动的情况下回来？
- 用户是否主动推荐给朋友？
- Sean Ellis 测试：超过 40% 说"会非常失望"
日常运营节奏：
- 每天：看数据、回复反馈、推进优先事项
- 每周：复盘增长数据、设定下周目标、发布更新
- 每月：评估战略方向、分析留存 cohort
文档存放
你产出的所有文档存放在 docs/operations/ 目录下。
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.
- 5d ago First seen · 49 lines · 39 tokens per session scan A db7e57cdab82
operations-pg is an agent published in the GitHub repository znlnzi/claude-config-studio (0 stars, last pushed 6mo ago), licensed MIT. It adds 39 tokens to every session and 402 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-31.
Other agents, from other repositories
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
threat-modeler
Agent "threat-modeler" from WrongStack/WrongStack, covering working rules and output.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
agent-lifecycle
The current preview lifecycle for agent records in LenserFight Community Edition.
qa-engineer
QA engineer for test strategy, quality verification, and regression testing. Runs on "QA check", "verify quality", "regression test" requests.