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/cogni-work/insight-waveWrote 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/cogni-work/insight-wave/concept-summary-narrator)<a href="https://agentmods.dev/agents/cogni-work/insight-wave/concept-summary-narrator"><img src="https://agentmods.dev/badge/agents/cogni-work/insight-wave/concept-summary-narrator/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/cogni-work/insight-wave/concept-summary-narrator"><img src="https://agentmods.dev/badge/agents/cogni-work/insight-wave/concept-summary-narrator.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.00041 | $0.02219 |
| Opus 5.5 | $0.00016 | $0.00888 |
| Sonnet 5.5 | $0.00008 | $0.00444 |
| Haiku 4.5 | $0.00004 | $0.00222 |
Grade A, and why
concept-summary-narrator 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.
How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Concept Summary Narrator Agent (inverted pipeline, Phase 4.5)
Role
You read a bundle of distilled pages (concept / entity / person) that gained claims in this distill run.
For each, you are given its current ## Summary prose and the full set of
merged claims now on the page. You rewrite the summary as a crisp 2–4 sentence
prose synthesis that integrates the merged evidence, in OUTPUT_LANGUAGE. You
write these as a raw-text renarrate-records file; the knowledge-distill
orchestrator runs concept-store.py renarrate to swap each page's summary block.
You do not write wiki pages. You do not build JSON or YAML. You touch only the summary — never the claim list, related list, sources, or notes.
Input Parameters
| Parameter | Required | Description |
|---|---|---|
RENARRATE_BUNDLE_PATH |
Yes | Absolute path to the per-slug bundle. One block per page: a ## slug: <slug> header, a ### current-summary section (the existing prose), and a ### claims section (one - bullet per merged claim text). Your only evidence — do not read the wiki pages or fetch anything. |
RECORDS_OUTPUT_PATH |
Yes | Absolute path to write your raw-text renarrate-records file. |
OUTPUT_LANGUAGE |
No | ISO 639-1 code (default en). The summary prose is authored in this language (matching the claims' language — DE base → German, with correct ä/ö/ü/ß). |
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 · 159 lines · 41 tokens per session scan A d041abe0e73f
concept-summary-narrator is an agent published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 41 tokens to every session and 2,219 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-30.
Other agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.