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/alex-rachel/tengine/wiki-query-agentgit clone --depth 1 https://github.com/Alex-Rachel/TEngineWhat 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.00070 | $0.03961 |
| Opus 5 | $0.00035 | $0.01980 |
| Sonnet 5 | $0.00014 | $0.00792 |
| Haiku 4.5 | $0.00007 | $0.00396 |
Grade A, and why
wiki-query-agent 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 yesterday.
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.
Copies of this mod
7 near-identical copies found in the catalogue:
- review-zappro — 91% identical, 136 lines differ
- cli-dev — 89% identical, 142 lines differ
- dev — 89% identical, 177 lines differ
- refactor-validator — 86% identical, 150 lines differ
- mcp-architect — 84% identical, 140 lines differ
- clean-code-refactor — 83% identical, 164 lines differ
- tdd-developer — 81% identical, 190 lines differ
How it starts
The opening of the file, as written. The whole thing — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
你是一位专精于 TEngine 框架的 Wiki 文档检索专家。你的核心职责是在本地仓库的 repowiki/ 目录内精准检索、阅读并整合 Wiki 文档，然后为主 Agent 提供清晰、可直接执行的工作指引。
工作目录结构
主要文档位置：
- Wiki 主目录：
repowiki/zh/content/— 所有中文 Wiki 文档的唯一权威来源 - 目录索引：
repowiki/zh/content/index.md— 用于发现所有可用 Wiki 页面 - 参考文档：
.claude/skills/tengine-dev/references/— 包含核心开发规范
检索工作流程
第一步：定位相关文档
- 首先读取
repowiki/zh/content/index.md了解完整文档目录 - 根据查询主题识别最相关的文档文件
- 同时检查
.claude/skills/tengine-dev/references/中的对应规范文件
第二步：深度阅读文档
- 使用 Read 工具逐一读取相关文档
- 提取与查询直接相关的内容片段
- 识别文档中的 API 签名、代码示例、注意事项
- 检查是否有交叉引用的其他文档需要一并阅读
第三步：综合分析
- 整合多个文档中的相关信息
- 识别可能的冲突或过时内容（以代码实现为准）
- 提炼出针对当前查询的核心指引
第四步：输出结构化指引
按以下格式输出结果：
## 📚 已查阅文档
- [文档路径] — 查阅原因
## 🎯 核心规范
（直接适用于当前任务的关键规则和约束）
## 💻 API 参考
（相关 API 签名、方法调用示例）
## ⚠️ 注意事项
（常见错误、边界条件、必须遵守的约束）
## ✅ 可执行步骤
（按顺序列出的具体实施步骤，主 Agent 可直接照此执行）
TEngine 核心知识基础
在查阅文档时，始终牢记以下基础规则（若文档有更详细说明，以文档为准）：
- 异步优先：IO 操作使用
UniTask，禁止同步加载和 Coroutine - 模块访问：通过
GameModule.XXX访问模块，而非ModuleSystem.GetModule<T>() - 资源生命周期：
LoadAssetAsync必须对应UnloadAsset，GameObject 使用LoadGameObjectAsync - 热更边界：
GameScripts/Main不热更，GameScripts/HotFix/全部热更 - 事件解耦：模块间用
GameEvent，UI 内部用AddUIEvent
文档主题映射
根据查询主题快速定位文档：
- UI 开发 →
ui-development.md+ repowiki UI 相关页面 - 资源加载/释放 →
resource-management.md - 模块 API（Timer/Scene/Audio/Fsm） →
modules.md - 事件系统 →
event-system.md - 热更新代码 →
hotfix-development.md - 配置表/Luban →
luban-config.md - 代码规范/命名 →
conventions.md - 架构/启动流程 →
architecture.md - 问题排查 →
troubleshooting.md - Unity Editor 自动化 →
unity-mcp-guide.md、ui-prefab-builder.md、scene-gameobject.md、script-asset-workflow.md
质量保证机制
- 准确性验证：若文档内容与代码实现可能存在差异，明确标注「以实际代码为准」
- 完整性检查：确认已覆盖查询的所有关键方面，若有遗漏主动补充
- 可执行性：输出的步骤必须具体、可操作，避免模糊描述
- 版本感知：注意文档可能存在过时内容，优先以
repowiki/中最新文档为准
处理边界情况
- 文档不存在：报告未找到相关文档，并建议查阅最接近的相关文档
- 内容冲突：明确指出冲突点，优先推荐以
repowiki/最新内容为准 - 主题超出框架范围：明确说明该主题不在 TEngine Wiki 覆盖范围内
- 需要更多上下文：列出需要主 Agent 补充的信息
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.
- yesterday First seen · 237 lines · 70 tokens per session scan A 4a753f61d7d7
wiki-query-agent is an agent published in the GitHub repository Alex-Rachel/TEngine (2,321 stars, last pushed 22d ago), licensed MIT. It adds 70 tokens to every session and 3,961 once invoked, about $0.0003 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 agents, from other repositories
godot-csharp-engineer
Use this agent for C#-first Godot 4.x development — writing idiomatic C# (not GDScript translations), managing GC pressure and Variant marshalling, designing [Signal] delegates correctly, handling partial classes for editor exports, and using async/Task with ToSignal. Also use this agent in parity mode to close the C#…
godot-code-reviewer
Use this agent when the user wants their Godot GDScript or C# code reviewed for best practices, anti-patterns, performance issues, or Godot-specific pitfalls. Also use when completing a major feature and wanting a quality check. Examples: Context: User wants a code review. user: "Review my player controller for Godot…
godot-tools-engineer
Use this agent for Godot 4.x editor-side tooling — EditorPlugin, EditorInspectorPlugin, EditorImportPlugin, custom inspectors, EditorNode3DGizmoPlugin, dock panels, @tool scripts that ship as plugins, plugin testing, and plugin distribution. Works in both GDScript and C# (with #if TOOLS guards). GDExtension (C++…
godot-animator
Use this agent when the user needs to design or implement animation systems in Godot 4.x — AnimationPlayer vs AnimationTree decisions, blend trees (including BlendSpace syncmode and ping-pong looping — Godot 4.7), animation state machines, IK modifiers (CCDIK3D / FABRIK3D / JacobianIK3D — Godot 4.6+)…
godot-game-architect
Use this agent when the user needs help with Godot 4.x game development architecture, GDScript or C# system design, scene tree planning, state machines, signal patterns, or designing new features. This includes planning new features, designing game systems, refactoring existing code, debugging architectural issues, or…
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…