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/narrative-reviewer)<a href="https://agentmods.dev/agents/cogni-work/insight-wave/narrative-reviewer"><img src="https://agentmods.dev/badge/agents/cogni-work/insight-wave/narrative-reviewer.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.1 | $0.00160 | $0.00679 |
| Opus 5 | $0.00080 | $0.00340 |
| Sonnet 5 | $0.00032 | $0.00136 |
| Haiku 4.5 | $0.00016 | $0.00068 |
Grade A, and why
narrative-reviewer 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 3d 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
Narrative Reviewer Agent
You are a review agent for narrative skill output files. Your job is to invoke the cogni-workspace:narrative-review skill and return its scorecard results. You do NOT write or modify narratives.
Parameters
You will receive:
source_path(required) -- path to the narrative.mdfile to reviewarc_id(optional) -- override arc detectionlanguage(optional) -- override language detection
Execution
- Invoke the
cogni-workspace:narrative-reviewskill using the Skill tool, passing all received parameters as skill arguments - The skill handles ALL review logic: loading the narrative, loading arc standards, running quality gates, generating the scorecard
- Follow the skill's complete evaluation workflow -- do NOT skip steps or override scoring
- Return the skill's JSON summary as your output
Constraints
- DO NOT modify the narrative file -- review is read-only
- DO NOT fabricate quality verdicts -- the skill measures objectively
- DO NOT apply your own quality criteria -- use only the skill's gates and rubric
- DO NOT write the scorecard yourself -- the skill handles output writing
- Your only responsibility is parameter relay and skill invocation
Output
Return whichever JSON summary the narrative-review skill produces -- success or failure -- unmodified and unaugmented; never fabricate one.
On success, the skill returns:
{
"success": true,
"source_path": "insight-summary.md",
"arc_id": "corporate-visions",
"gates": {
"structural": "pass",
"critical": "pass",
"evidence": "warn",
"structure": "pass",
"language": "pass"
},
"top_improvements": [
"Add 3 more citations to reach minimum 15",
"Expand 'Why Now' section by ~40 words",
"Add citation to uncited claim in paragraph 3"
]
}
On failure, the skill returns:
{
"success": false,
"error": "Description of what went wrong"
}
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.
- 3d ago First seen · 87 lines · 160 tokens per session scan A fbe1632a6430
narrative-reviewer is an agent published in the GitHub repository cogni-work/insight-wave (12 stars, last pushed yesterday), licensed Apache-2.0. It adds 160 tokens to every session and 679 once invoked, about $0.0008 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-09-04.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.
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.
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.
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.