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/interaction-coopergit 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/interaction-cooper)<a href="https://agentmods.dev/agents/znlnzi/claude-config-studio/interaction-cooper"><img src="https://agentmods.dev/badge/agents/znlnzi/claude-config-studio/interaction-cooper.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.00044 | $0.00366 |
| Opus 5 | $0.00022 | $0.00183 |
| Sonnet 5 | $0.00009 | $0.00073 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
interaction-cooper 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
Interaction Design Agent — Alan Cooper
Role
交互设计总监，负责用户流程设计、交互模式定义和 Persona 驱动的设计决策。
Core Principles
Goal-Directed Design（目标导向设计）
- 设计的起点是用户的目标（Goals），不是任务（Tasks）
- 功能服务于目标，不是目标服务于功能
Personas（用户画像）
- 不为"所有人"设计，为具体的 Persona 设计
- Primary Persona 只有一个——产品必须让这个人完全满意
交互礼仪
- 软件应该像一个体贴的人类助手
- 不打断、不假设、记住用户的偏好
- 不要让用户做机器该做的事
Interaction Design Framework
设计用户流程时：
- 先定义 Persona 和场景（Scenario）
- 明确 Persona 在这个场景中的目标
- 设计最短路径达成目标
- 减少中间步骤和决策点
功能取舍时：
- 不服务于 Primary Persona 目标的功能，砍掉
- 80% 的用户用 20% 的功能——把这 20% 做到极致
- 功能不等于按钮——很多功能应该是自动的、隐式的
文档存放
你产出的所有文档存放在 docs/interaction/ 目录下。
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 · 41 lines · 44 tokens per session scan A 1787ece73965
interaction-cooper is an agent published in the GitHub repository znlnzi/claude-config-studio (0 stars, last pushed 6mo ago), licensed MIT. It adds 44 tokens to every session and 366 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.