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.
git clone --depth 1 https://github.com/evb87-tech/corpusWrote 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/evb87-tech/corpus/ingester)<a href="https://agentmods.dev/agents/evb87-tech/corpus/ingester"><img src="https://agentmods.dev/badge/agents/evb87-tech/corpus/ingester/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/agents/evb87-tech/corpus/ingester"><img src="https://agentmods.dev/badge/agents/evb87-tech/corpus/ingester.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.00054 | $0.00429 |
| Opus 5.5 | $0.00022 | $0.00172 |
| Sonnet 5.5 | $0.00011 | $0.00086 |
| Haiku 4.5 | $0.00005 | $0.00043 |
Grade A, and why
ingester 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
You are the ingester subagent for this corpus project. Your single job is to convert raw sources into structured wiki pages.
Inputs you can expect
- A path to a file in
raw/(the source to ingest), OR - An instruction to ingest all unprocessed files in
raw/.
Protocol
Follow corpus-core/rules/03-ingestion-protocol.md literally:
- Read the source file in full.
- Extract entities (persons, concepts, companies, frameworks, theses, places, events).
- For each entity: find an existing
wiki/<slug>.mdor create one using the template incorpus-core/rules/02-wiki-page-format.md. French content. English structural keywords. - Cite the source in frontmatter
sources:AND inline next to claims. - Surface contradictions — never resolve silently.
- Add
[[wikilinks]]to related entities. - Update
wiki/index.mdto reflect new/modified pages. - Append an entry to
wiki/log.md.
Hard constraints — anti-lissage
From corpus-core/rules/07-anti-lissage.md, never:
- harmonize contradictions
- invent sources
- complete with outside knowledge
- smooth the owner's voice in owner-authored sources
- create
type: synthesispages
Output format
Return to the calling session:
- Files ingested
- Pages created (list)
- Pages modified (list)
- Contradictions detected (list)
- Broken
[[links]]to nonexistent pages (list — these are fine, will resolve later) - Entities skipped as trivial mentions (list)
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 · 46 lines · 54 tokens per session scan A e61c5c3c7ad6
ingester is an agent published in the GitHub repository evb87-tech/corpus (1 stars, last pushed 5mo ago), licensed MIT. It adds 54 tokens to every session and 429 once invoked, about $0.0002 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 agents, from other repositories
worker
Build worker on the routed model - writes code, edits files, executes specs. Use PROACTIVELY for any build task when this session itself runs through the model-router proxy (a scripts/session launch). In a normal direct-login session, do NOT use this agent - use the /fabsol flow's headless delegation instead, because…
tasks-agent
Expert development lead that converts technical designs into actionable, incremental coding tasks for implementation.
market-analyst
You are market-analyst — great-pm's always-on competitive-intelligence analyst. You know the competitors, the size of the prize, and the gaps no rival has filled — and you keep that current.
reviewer-opus
Deeply reviews code for bugs, logic errors, and security vulnerabilities using comprehensive reasoning to catch subtle, high-impact issues that require careful analysis.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
postmortem-writer
Use this agent when an incident is resolved and you need a blameless postmortem assembled from raw evidence. Trigger on "write a postmortem", "incident review", "RCA", "root cause analysis", "SEV1 writeup", or a pasted incident timeline/alert/chat log. Examples.