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 commands/avos-lab/git-aware-coding-agent/askgit clone --depth 1 https://github.com/Avos-Lab/git-aware-coding-agentWhat 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.00000 | $0.00687 |
| Opus 5 | $0.00000 | $0.00344 |
| Sonnet 5 | $0.00000 | $0.00137 |
| Haiku 4.5 | $0.00000 | $0.00069 |
Grade A, and why
ask 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
avos ask
Ask a natural-language question about the repository and get an evidence-backed answer.
Usage
avos ask <question>
avos --json ask <question>
Options
| Option | Description |
|---|---|
question |
Natural language question about the repository (required) |
Global Options
| Option | Description |
|---|---|
--json |
Emit machine-readable JSON output (for AI agents/automation) |
Examples
avos ask "How does authentication work?"
avos ask "What was the rationale for the retry scheduler?"
avos ask "Who worked on the payment module?"
# JSON mode for AI agents
avos --json ask "How does authentication work?"
JSON Output Mode
When --json is passed, output is strict JSON conforming to the avos.ask.v1 schema:
{
"success": true,
"data": {
"format": "avos.ask.v1",
"raw_text": "...",
"answer": { "text": "..." },
"evidence": {
"is_none": false,
"items": [
{ "line_raw": "...", "kind": "PR", "id": "#123", "title": "...", "author": "...", "date_label": "Mar 2026" }
],
"unparsed_lines": []
},
"parse_warnings": []
},
"error": null
}
On failure, the envelope contains "success": false with an error object:
{
"success": false,
"data": null,
"error": {
"code": "CONFIG_NOT_INITIALIZED",
"message": "...",
"hint": "Run 'avos connect org/repo' first.",
"retryable": false
}
}
JSON mode requires the reply model configuration (see below).
Reply Output (Optional)
To get clean, decorated terminal output (and enable JSON mode), set these environment variables (e.g. in .env):
| Variable | Description |
|---|---|
REPLY_MODEL |
Model identifier (e.g. Qwen/Qwen3-Coder-30B-A3B-Instruct) |
REPLY_MODEL_URL |
API endpoint (OpenAI-compatible chat completions) |
REPLY_MODEL_API_KEY |
API key for the reply model |
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 · 94 lines · 0 tokens per session scan A 6b067057ef04
ask is a command published in the GitHub repository Avos-Lab/git-aware-coding-agent (2 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 687 tokens. 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 commands, from other repositories
add-agent
引导新增一个 Agent 适配器。用法 /add-agent.
backfill-auto
.opensunstar/wiki/candidates/rd-backfill-auto- / ├── candidate.json # engine: "rd-backfill-auto", sourcecommit, createdat └── wiki/ ├── index.md └── runbooks/ .md # wiki schema frontmatter.
extract-routing
Command "extract-routing" from alisunstar/OpenSunstar, covering /rd:extract-routing — 源码锚点提取适配器（外置）, 先读规则, 执行, 产物 and 何时停止.
verify-prd
Command "verify-prd" from alisunstar/OpenSunstar, covering /rd:verify-prd — 输入质量门禁, 先读规则, 执行, 何时澄清 and 何时停止.
wrap
Close the session cleanly. Update entity state. Capture decisions. Detect momentum shifts.
code-review
Command "code-review" from alisunstar/OpenSunstar, covering /rd:code-review — 代码审查, 先读, 执行, 产物 and 人工确认.