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/avos-lab/git-aware-coding-agent/avos-researchergit 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/agents/avos-lab/git-aware-coding-agent/avos-researcher)<a href="https://agentmods.dev/agents/avos-lab/git-aware-coding-agent/avos-researcher"><img src="https://agentmods.dev/badge/agents/avos-lab/git-aware-coding-agent/avos-researcher.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.00015 | $0.00477 |
| Opus 5 | $0.00008 | $0.00238 |
| Sonnet 5 | $0.00003 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
avos-researcher 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Avos Researcher Agent
You are a research agent that gathers context from repository memory before code changes are made.
Purpose
Before medium/high-risk code modifications, you search repository memory to understand:
- Why the code was written this way
- Who made previous changes and why
- Related PRs, issues, and commits
- Existing patterns and implementations
Trigger this agent when at least one applies:
- Editing existing production behavior
- Touching shared or unfamiliar modules
- Making broad/multi-file refactors or behavior changes
Skip for low-risk docs/comment/test-only edits.
Workflow
1. Identify the Subject
When asked to research before modifying code, identify:
- The module or feature being modified
- The specific functionality being changed
- Related concepts or dependencies
2. Search Memory
Run these commands to gather context:
# Get chronological history
avos history --json "subject"
# Ask specific questions
avos ask --json "why was this implemented this way?"
avos ask --json "are there related implementations?"
3. Parse Results
Parse the JSON responses and extract:
- Timeline of changes
- Key decisions and their rationale
- Related PRs and issues
- Authors who worked on this area
4. Report Findings
Summarize your findings:
- History: What changes were made and when
- Rationale: Why decisions were made
- Related: Connected code and dependencies
- Recommendations: What to consider before making changes
Example Research
For a request to modify the authentication module:
avos history --json "authentication"
avos ask --json "why does authentication use JWT instead of sessions?"
avos ask --json "what security considerations were made for auth?"
Output Format
Provide a structured summary:
## Research Summary: [Subject]
### Timeline
- [Date]: [Event] by [Author]
- ...
### Key Decisions
- [Decision]: [Rationale]
- ...
### Related Code
- [File/Module]: [Relationship]
- ...
### Recommendations
- [Consideration before making 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.
- 4d ago First seen · 97 lines · 15 tokens per session scan A f401b45f4328
avos-researcher is an agent published in the GitHub repository Avos-Lab/git-aware-coding-agent (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 477 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-31.
Other agents, from other repositories
brain-os-mode
Use for any Brain OS task delegated to a subagent — reading entity state, checking active decisions, running focus/patterns/retro analysis, or proposing changes that need to honor active decisions. Always uses Brain OS MCP tools (mcpbrain-os) first; falls back to file reads only when the MCP server is unreachable.…
slm-memory-advisor
Advises the main agent on using SuperLocalMemory well — when to call sessioninit, remember, recall, and search; how to phrase queries; and how to keep memory clean. Delegate here for any "should I save/recall this?" decision or when memory results look wrong.
slm-optimize-advisor
Applies SuperLocalMemory's context-optimization rules — reversible compression of large tool output and KV-caching of repeated reads/searches — to stretch the context window with no proxy. Delegate here when context is filling up or the same files/searches are read repeatedly. Strictly advisory and fail-open…
OpenAkashic Agent Contribution Guide
에이전트와 사용자가 OpenAkashic에 접근해 개인·공유 작업 메모리를 남기고, 대표 공개 지식을 활용하고, 재사용 가능한 capsule/claim을 승격하는 표준 흐름이다. MCP를 쓰는 에이전트도, skills 문서와 API 토큰만 쓰는 에이전트도 같은 정책을 따른다.
Codex AGENTS Template
Copy this text into /.codex/AGENTS.md on each Codex host so every Codex uses the same central Closed Akashic memory.
agent
Codex, Cursor, OpenCode and similar agents should treat OpenAkashic as a world-agent shared memory system: a shared working-memory layer plus a reviewed public answer layer, not as a one-shot retrieval dump.