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/xsovad06/sova/ingest-reviewgit clone --depth 1 https://github.com/xsovad06/sovaWrote 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/xsovad06/sova/ingest-review)<a href="https://agentmods.dev/commands/xsovad06/sova/ingest-review"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/ingest-review.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.00020 | $0.00777 |
| Opus 5 | $0.00010 | $0.00388 |
| Sonnet 5 | $0.00004 | $0.00155 |
| Haiku 4.5 | $0.00002 | $0.00078 |
Grade A, and why
ingest-review 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ingest PR Review Feedback
Parse structured review findings from TaskRun records and update agent memory.
Instructions
-
Get the PR number from
$ARGUMENTS. If empty, ask the user. -
Query the database for reviewer TaskRun records linked to this PR:
# Find the reviewer run's handoff data python3 -c " import asyncio, json, os os.environ.setdefault('SOVA_DATABASE_URL', 'sqlite+aiosqlite://.claude/sova.db') from sova.db.session import init_db, get_session from sova.db.models import TaskRun from sqlalchemy import select async def main(): await init_db(run_migrations=False) async with get_session() as session: stmt = select(TaskRun).where( TaskRun.pr_number == <PR_NUMBER>, TaskRun.role.in_(['reviewer', 'command:review-pr']), TaskRun.status == 'done', ).order_by(TaskRun.id.desc()).limit(1) run = (await session.execute(stmt)).scalar_one_or_none() if not run or not run.handoff_json: print('NO_FINDINGS') return print(json.dumps(run.handoff_json, indent=2)) asyncio.run(main()) " -
If the output is
NO_FINDINGS, report "No reviewer findings found for PR #N" and stop. -
Parse the
pending_findingsarray from the handoff JSON. Each finding has:file: file pathline: line numberseverity: 1-10 scorecategory: type of issue (bug, style, performance, etc.)description: what the issue issuggestion: how to fix it
-
Also fetch external review comments (CodeRabbit, human reviewers):
gh pr view <PR_NUMBER> --json reviews,comments --jq '.reviews[] | {author: .author.login, state: .state, body: .body}' -
Classify findings into memory categories:
- Severity >= 7: likely a "common_mistake" -- check
.claude/agent-memory/cookbook.mdfor existing entries - Severity 4-6 with "style" or "naming" category: "style preference"
- Repeated patterns across findings: "review pattern" worth codifying
- Test-related findings: "test coverage gap"
- Severity >= 7: likely a "common_mistake" -- check
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 · 89 lines · 20 tokens per session scan A dea9b25df7bb
ingest-review is a command published in the GitHub repository xsovad06/sova (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 20 tokens to every session and 777 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 commands, from other repositories
retro
Post-work command that extracts learnings and updates the learning registry.
aprende
Review the current conversation and save reusable learnings (memory, lesson, skill stub, project-doc) after confirmation. / Revisa la conversación actual y guarda aprendizajes reusables con confirmación.
mem-search
Search past observations and context from claude-mem persistent memory.
bos-learn
Add a memory manually to the BOS self-evolving memory system.
bos-search
Search the BOS context cache using semantic similarity.
bos-sync-karimo
Sync KARIMO learnings and PRD artifacts to the BOS context and memory systems.