Borrowing it
Nothing to install: this file belongs to Avos-Lab/git-aware-coding-agent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Avos-Lab/git-aware-coding-agent/main/.claude/commands/avos-history.mdgit 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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<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="Reviewed on agentmods" width="80" 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.1 | $0.00009 | $0.00172 |
| Opus 5.5 | $0.00004 | $0.00069 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (4 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 9 tokens to every session and 172 once invoked, about $0.0000 per session on Opus 5.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
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
queue
"What's coming up — plan steps, releases, backlog, and overdue decisions?".
gsd-remove-phase
Remove a future phase from roadmap and renumber subsequent phases.
review-code
Read ALL memory bank code rules + best practices, check the files that changed, and APPLY fixes so they adhere. The active counterpart to /scan (which is read-only). Use after an AI session, before commit, to make changed files compliant.
clarify
A command for resolving unanswered questions in a product requirement before technical analysis. It records the questions and agreed answers in a clarification document.
decide
Capture a strategic decision so it never gets lost or reopened accidentally.