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 skills/khazixw2/everything-maa/maa-interface-guidenpx skills add KhazixW2/Everything-Maa --skill maa-interface-guidegit clone --depth 1 https://github.com/KhazixW2/Everything-MaaWrote 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/khazixw2/everything-maa/maa-interface-guide)<a href="https://agentmods.dev/skills/khazixw2/everything-maa/maa-interface-guide"><img src="https://agentmods.dev/badge/skills/khazixw2/everything-maa/maa-interface-guide.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 | $0.00084 | $0.01279 |
| Opus 5 | $0.00042 | $0.00639 |
| Sonnet 5 | $0.00017 | $0.00256 |
| Haiku 4.5 | $0.00008 | $0.00128 |
Grade A, and why
maa-interface-guide 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 4d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maa Interface V2 工作流
只处理已存在的 Project Interface V2。先确定用户要求的是解释、审查/诊断还是修改;只读请求不得改文件。
建立事实基线
- 在目标项目中定位
interface.json或interface.jsonc。不存在时停止,要求先使用$maa-project-create创建项目;不得生成孤立的 Interface。 - 读取
interface_version。只接受 V2;缺失、为 1 或呈现 v1 结构时报告不支持,不提供迁移或兼容写法。 - 先读取目标项目已有的 schema 关联、MaaFramework 版本锁、
maatools.config.mts、Interface import 和语言文件。项目内证据优先于本 skill 的经验。 - 若项目没有足够的协议依据,再查 MaaFramework 官方仓库当前对应版本的文档与
tools/interface*.schema.json。记录实际采用的 tag、commit、schema 路径或 URL;不要依赖个人机器上的 MaaFramework 绝对路径。 - 保留目标文件现有的 JSON/JSONC、缩进、字段排序、命名和拆分风格,除非用户明确要求统一格式。
需要检查字段选择与引用关系时读取 references/review-guide.md。需要选择和运行验证工具时读取 references/validation.md。
操作模式
解释
只读主文件、import、语言文件及相关 Pipeline 入口,说明 controller、resource、task、group、option、preset 和 setting 的实际关系。区分“schema 允许”“Client 可能支持”和“当前项目确实使用”,不要把推断表述成事实。
审查或诊断
按以下顺序检查并报告带文件位置的证据:
- V2 版本与 schema 合法性;
- import、资源路径、图标、语言文件等路径是否可解析;
- controller、resource、group、task、option、case、input、preset 和 locale 引用是否存在且唯一;
- controller/resource 过滤后,task、option、preset 与 setting 是否仍然适用;
- task entry 是否能在所选资源的 Pipeline 中解析;
pipeline_override是否只覆盖已存在的节点;- Interface 配置和多语言内容是否完整;
- 项目已有校验工具的诊断结果。
审查请求默认不修复。区分协议错误、跨文件语义错误、Client 兼容风险和维护性建议。
修改
- 先列出受影响的声明、引用和 controller/resource 组合。
- 仅修改主 Interface、其 import、语言文件和 Interface 配置文件。
- 做最小闭环修改;同步更新允许范围内的引用和翻译,不顺手重排无关字段。
- Pipeline、Python Agent、图片和构建配置只读。需要修改这些文件时按“技能接力”处理。
- 修改后执行“验证与完成标准”。
技能接力
- 目标项目或 Interface 不存在:停止并使用
$maa-project-create;本 skill 不创建项目或 Interface。 - option 的 Interface 声明由本 skill 负责;一旦涉及
pipeline_override行为、目标 Pipeline 节点或 Python 参数读取,使用$maa-pipeline-option。 - Pipeline 节点、识别、动作或状态流设计使用
$maa-pipeline-guide;行为验证使用$maa-pipeline-testing;关系可视化使用$maa-pipeline-graph。 - 用户要求完整功能时,可以显式接力对应 skill 并继续闭环。用户只要求 Interface 审查或修改时,不得扩大写入范围,只报告跨边界问题。
验证与完成标准
按 references/validation.md 从低成本到高成本验证:JSON/JSONC 解析、项目 schema、路径与引用、项目已有检查命令、可选的 maa-tools 语义诊断。运行 maa-tools 前先检查 package.json 中已有的脚本和项目实际使用的包管理器;有项目脚本或已安装依赖时使用项目锁定命令,禁止直接执行 node_modules 内文件。静态编辑不得自动连接设备或执行 Pipeline。解释或只读审查中,若检查命令会写日志、缓存或其他文件,必须先取得用户许可。
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 70 lines · 84 tokens per session scan A df28f7f99f8e
maa-interface-guide is a skill published in the GitHub repository KhazixW2/Everything-Maa (12 stars, last pushed yesterday), licensed MIT. It adds 84 tokens to every session and 1,279 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…