ingest-pr

A command that fetches one pull request, which is a proposed set of code changes, and saves its details in Avos Memory for later queries.

In plain words
What is it for?
Run it with a repository such as org/repo and a pull-request number to record that change, optionally receiving machine-readable JSON output.
Why use it?
It keeps pull-request context available after the change is pushed and skips storing the same content again.

Command

Install

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.

agentmods
npx agentmods add commands/avos-lab/git-aware-coding-agent/ingest-pr
Clone the repo
git clone --depth 1 https://github.com/Avos-Lab/git-aware-coding-agent
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 708 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00708
Opus 5 $0.00000 $0.00354
Sonnet 5 $0.00000 $0.00142
Haiku 4.5 $0.00000 $0.00071

Measured yesterday against content hash 146d94e25d4a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ingest-pr 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.

docs/user/commands/ingest-pr.md · 121 lines

How it starts

The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.

avos ingest-pr

Ingest a single PR into Avos Memory.

Usage

avos ingest-pr [--json] <org/repo> <pr_number>

Description

Fetches a single PR by number, builds its artifact, and stores it in Avos Memory. Use this after pushing a PR to ensure its context is available for future queries.

The command automatically skips PRs that have already been ingested (based on content hash).

Arguments

Argument Description
org/repo Repository slug in 'org/repo' format
pr_number PR number to ingest

Options

Option Description
--json Emit machine-readable JSON output

Output

Human-Readable (default)

┌─ PR #123 Ingested ───────────────────────────────┐
│ Title: Add authentication module                 │
│ Author: developer                                │
│ Files: 5                                         │
│ Note ID: note-abc-12...                          │
└──────────────────────────────────────────────────┘

When skipped (already ingested):

PR #123 already ingested. Skipping.

JSON Output

Stored:

{
  "success": true,
  "data": {
    "pr_number": 123,
    "action": "stored",
    "note_id": "note-abc-123",
    "reason": null
  },
  "error": null
}

Skipped (already ingested):

{
  "success": true,
  "data": {
    "pr_number": 123,
    "action": "skipped",
    "note_id": null,
    "reason": "already_ingested"
  },
  "error": null
}

Exit Codes

Code Meaning
0 Success (stored or skipped)
1 Precondition failure (bad args)
2 Hard external failure (API error)

Examples

# Ingest PR #123 from myorg/myrepo
avos ingest-pr myorg/myrepo 123

# Ingest with JSON output
avos ingest-pr --json myorg/myrepo 123

# Use in a script after pushing
PR_NUM=$(gh pr view --json number -q .number)
avos ingest-pr --json myorg/myrepo "$PR_NUM"

Read the full file on GitHub · 121 lines

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.

  1. yesterday First seen · 121 lines · 0 tokens per session scan A 146d94e25d4a

Subscribe to this mod's changes

ingest-pr 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 708 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.