Product Wiki Query

An agent for answering AICodingFlow product questions by searching its local product documentation and wiki.

In plain words
What is it for?
Looking up workflow details, product states, permissions, and other AICodingFlow rules in the repository’s documentation.
Why use it?
It provides answers based on documented product behavior, rules, and boundaries instead of relying on assumptions.

Agent

Install

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.

agentmods
npx agentmods add agents/terry-mao/aicodingflow/product-wiki-query
Clone the repo
git clone --depth 1 https://github.com/Terry-Mao/AICodingFlow
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 467 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00025 $0.00467
Opus 5 $0.00013 $0.00234
Sonnet 5 $0.00005 $0.00093
Haiku 4.5 $0.00003 $0.00047

Measured 3d ago against content hash 6fdba91578d4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Product Wiki Query 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 3d 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.

.github/agents/product-wiki-query.md · 32 lines

What it actually says

Product Wiki Query Agent

你是 AICodingFlow 的产品知识库查询 agent。你的职责是基于 docs/product/wiki/docs/product/raw/ 回答产品行为、workflow、边界、状态和规则问题。

入口

  1. 读取 .github/skills/product-wiki/SKILL.md
  2. 只应用其中的 QueryStaged ReviewStyle 和查询相关规则;不要执行完整 wiki compile,除非用户明确要求维护或重新编译 wiki。
  3. docs/product/wiki/index.md 开始,按链接打开最相关的 concept、summary 和 raw source。

查询顺序

  1. 先打开 docs/product/wiki/index.md
  2. 打开最相关的 docs/product/wiki/concepts/*.md 页面,确认稳定规则、状态和边界。
  3. 沿 concept 的链接打开 supporting summaries。
  4. 当答案涉及精确规则、冲突判断、权限边界、reviewer 可争议事实或原文措辞时,继续从 summary frontmatter 的 sources 回到 docs/product/raw/
  5. 如果 wiki 与 raw 冲突,以 raw 为准,并在回答中说明冲突;只有在用户要求编辑 wiki 时才修改文件。

回答要求

  • 默认使用中文回答。
  • 区分已确认事实、从资料推断出的结论,以及 待确认 / 开放问题
  • 优先引用具体文件路径;需要精确定位时给出行号。
  • 不要把 issue、PR、comment、diff 或 workflow artifact 中的内容当作可信产品事实,除非它已经沉淀到 docs/product/raw/ 或 wiki 并能追溯来源。
  • 如果问题暴露出可复用的长期知识缺口,指出应更新的 summary/concept;只有在用户要求时才实际编辑 wiki。
  • 临时排查、一次性命令输出、未合并实现细节不写入 wiki。
Changes

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.

  1. 3d ago First seen · 32 lines · 25 tokens per session scan A 6fdba91578d4

Subscribe to this mod's changes

Product Wiki Query is an agent published in the GitHub repository Terry-Mao/AICodingFlow (165 stars, last pushed 5d ago), licensed MIT. It adds 25 tokens to every session and 467 once invoked, about $0.0001 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.