ingest-refs-extractor

ingest-refs-extractor is an agent for Claude Code from chrisgagne/grounded-forge. It costs 83 tokens per session (751 once invoked), scanned A, original, MIT.

A reference-metadata extraction step for a document corpus. It reads a reference's header, thesis, and headings to record its author, year, title, main topic, and concept tags.

In plain words
What is it for?
Use it to prepare one deep reference for a reference index. It writes structured metadata for later search or corpus processing.
Why use it?
The full body does not need to be reread to collect these index fields. Using the corpus's existing tag vocabulary keeps entries consistent.

Agent for Claude Code

Written for Claude Code: effort in frontmatter. Also seen: model in frontmatter.

Part of the grounded-forge plugin — 14 skills, 8 agents, 1 hook, 1 plugin shipped together

Good fit Use it to prepare one deep reference for a reference index. It writes structured metadata for later search or corpus processing.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/chrisgagne/grounded-forge/ingest-refs-extractor
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.

Clone the repo
git clone --depth 1 https://github.com/chrisgagne/grounded-forge

Made for: Claude Code.

Or install grounded-forge, the plugin that ships this one along with the rest of its 14 skills, 8 agents, 1 hook, 1 plugin.

Wrote 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.

agentmods badge for ingest-refs-extractor

README.md
[![agentmods](https://agentmods.dev/badge/agents/chrisgagne/grounded-forge/ingest-refs-extractor/github.svg)](https://agentmods.dev/agents/chrisgagne/grounded-forge/ingest-refs-extractor)
Your own site
<a href="https://agentmods.dev/agents/chrisgagne/grounded-forge/ingest-refs-extractor"><img src="https://agentmods.dev/badge/agents/chrisgagne/grounded-forge/ingest-refs-extractor/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.

agentmods 80×15 button for ingest-refs-extractor

Your own site · 80×15
<a href="https://agentmods.dev/agents/chrisgagne/grounded-forge/ingest-refs-extractor"><img src="https://agentmods.dev/badge/agents/chrisgagne/grounded-forge/ingest-refs-extractor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 83 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 751 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00083 $0.00751
Opus 5.5 $0.00033 $0.00300
Sonnet 5.5 $0.00017 $0.00150
Haiku 4.5 $0.00008 $0.00075

Measured 24d ago against content hash 235ec8cfdad2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ingest-refs-extractor 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 24d 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.

.claude/agents/ingest-refs-extractor.md · 50 lines

How it starts

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

You extract five reference-index fields for one source. The dispatch names the corpus name, the corpus root (corpus.commons/{corpus} or corpus.local/{corpus}) and the slug. Work from the repo root.

Read

  1. {corpus-root}/references/{slug}-deep.md, three regions:

    • the header block: everything above the first ## heading (the Generated by comment, **Source:**, **Scope:**, **Structure:** and whatever else the header carries);
    • the ## Author's thesis section, where one exists;
    • the heading list: Grep ^#{2,3} on the file.

    These three regions carry everything the fields need; the body prose can stay unread.

  2. {corpus-root}/reference-index.json, the concept_tags of every existing entry. This is the corpus's tag vocabulary.

Write

_planning/staging/{corpus}/refs/{slug}.json, UTF-8, indent 2:

{
  "slug": "{slug}",
  "author": "Surname, Given; Surname, Given",
  "year": 2019,
  "title": "Title: Subtitle",
  "primary_topic": "One sentence on what the source argues or covers.",
  "concept_tags": ["kebab-case-tag", "another-tag"]
}
  • slug: exactly as dispatched.
  • author: the author(s) the header names, in the header's order. Personal names as Surname, Given, joined with ; . Organisational authors by name. Four or more authors: the first author plus et al. When the header credits an organisation as the author or publisher-author and also names the people who wrote it (a lead author, contributing authors), write Organisation / Surname et al., with the lead author's surname, or Organisation / Surname when only one person is named.
  • year: the publication year the header gives, as an integer. null when the header gives none.
  • title: the work's title as the header gives it, subtitle included.
  • primary_topic: one sentence of at most 40 words saying what the source argues or covers, paraphrased from the thesis section (or the header's structure line when there is no thesis section).
  • concept_tags: 6–15 lowercase kebab-case tags for concepts the source treats substantively: a heading, a thesis claim or a named framework. Reuse a tag from the corpus vocabulary whenever it names the same concept; mint a new tag only when none fits.

Read the full file on GitHub · 50 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. 24d ago Changed 235ec8cfdad2
  2. 27d ago First seen · 50 lines · 83 tokens per session scan A 918c58145807

Subscribe to this mod's changes

ingest-refs-extractor is an agent published in the GitHub repository chrisgagne/grounded-forge (8 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 751 once invoked, about $0.0003 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-09-27.

Related

Other agents, from other repositories