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/avos-historygit clone --depth 1 https://github.com/Avos-Lab/git-aware-coding-agentWrote 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/commands/avos-lab/git-aware-coding-agent/avos-history)<a href="https://agentmods.dev/commands/avos-lab/git-aware-coding-agent/avos-history"><img src="https://agentmods.dev/badge/commands/avos-lab/git-aware-coding-agent/avos-history.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.00009 | $0.00172 |
| Opus 5 | $0.00005 | $0.00086 |
| Sonnet 5 | $0.00002 | $0.00034 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
avos-history 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.
What it actually says
Avos History
Get the chronological history of a subject in the repository.
Usage
Run this command and parse the JSON output:
avos history --json "$ARGUMENTS"
Response Handling
Parse the JSON response:
{
"success": true,
"data": {
"format": "avos.history.v1",
"timeline": { "months": [...] },
"summary": { "text": "..." }
}
}
If success is false, check error.code and error.hint for guidance.
Examples
- "authentication module"
- "user registration flow"
- "database connection handling"
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.
- 3d ago First seen · 41 lines · 9 tokens per session scan A 7b38d811bdc3
avos-history 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 adds 9 tokens to every session and 172 once invoked, about $0.0000 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 commands, from other repositories
add-agent
引导新增一个 Agent 适配器。用法 /add-agent.
extract-routing
Command "extract-routing" from alisunstar/OpenSunstar, covering /rd:extract-routing — 源码锚点提取适配器（外置）, 先读规则, 执行, 产物 and 何时停止.
decide
Capture a strategic decision so it never gets lost or reopened accidentally.
scorecard
Run a repeatable weekly health check. Score Brain OS out of 100. Compare week-over-week.
clarify
Command "clarify" from alisunstar/OpenSunstar, covering /rd:clarify — 澄清, 先读, 执行, 产物 and 人工确认.
release-plan
Command "release-plan" from alisunstar/OpenSunstar, covering /rd:release-plan — 发布计划, 先读, 执行, 产物 and 人工确认.