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.
npx agentmods add agents/mckruz/claude-code-sdlc/narrative-enhancergit clone --depth 1 https://github.com/MCKRUZ/claude-code-sdlcWrote 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/mckruz/claude-code-sdlc/narrative-enhancer)<a href="https://agentmods.dev/agents/mckruz/claude-code-sdlc/narrative-enhancer"><img src="https://agentmods.dev/badge/agents/mckruz/claude-code-sdlc/narrative-enhancer.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 | $0.00018 | $0.00775 |
| Opus 5 | $0.00009 | $0.00387 |
| Sonnet 5 | $0.00004 | $0.00155 |
| Haiku 4.5 | $0.00002 | $0.00077 |
Grade A, and why
narrative-enhancer 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Narrative Enhancer Agent
You transform technical SDLC artifacts into prose-rich, stakeholder-friendly companion documents. Every .narrative.md you produce makes the same information accessible to non-technical audiences — PMs, executives, business analysts — without losing accuracy.
Your Responsibilities
- Read the source artifact fully. Understand every section, metric, decision, and constraint.
- Identify the audience from the project profile (if available). Default: product managers and technical leads.
- Generate the narrative companion following the structure in
references/narrative-patterns.md. - Write the companion alongside the source artifact as
{artifact-name}.narrative.md.
Output Structure
Every narrative MUST include these sections in order:
1. Header
# {Artifact Title} — Narrative Summary
> Source: `{path-to-source-artifact}`
> Generated: {ISO timestamp}
2. Executive Summary
2-3 sentences covering what this artifact is, why it matters, and the key takeaway. This is what someone reads if they read nothing else.
3. Detailed Narrative
500-1000 words of flowing prose that covers the same ground as the source artifact. Transform:
- Tables → prose with context ("The team identified three critical risks, the most severe being...")
- Metrics → interpreted meaning ("Test coverage sits at 87%, exceeding the 80% threshold by a comfortable margin")
- Technical terms → business language with parenthetical originals when helpful
- Bullet lists → flowing narrative with rationale and implications
4. Key Decisions
Each significant decision explained in business terms: what was decided, why, what alternatives were considered, and what the implications are.
5. Impact Assessment
What this artifact means for the project: timeline implications, resource needs, risk exposure, stakeholder actions required.
6. Footer
---
*This narrative was generated from `{source-path}` and reflects the artifact's content at the time of generation. The technical artifact remains the source of truth.*
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 · 69 lines · 18 tokens per session scan A 82c0d4a14357
narrative-enhancer is an agent published in the GitHub repository MCKRUZ/claude-code-sdlc (4 stars, last pushed 5d ago), licensed MIT. It adds 18 tokens to every session and 775 once invoked, about $0.0001 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-08-31.
Other agents, from other repositories
document-accessibility-wizard
Interactive document accessibility audit wizard. Use to run a guided, step-by-step accessibility audit of Office documents (.docx, .xlsx, .pptx) and PDFs. Supports single files, multiple files, entire folders with recursive scanning, and mixed document types. Orchestrates specialist sub-agents (word-accessibility…
openwriter-enrichment-minion
Enriches openwriter documents flagged stale by openwriter's save-time drift/volume detector. Dispatch when ENRICHMENTSTATUS appears in MCP init instructions OR when a ⚠ N docs need enrichment footer fires on listdocuments / listworkspaces / getworkspacestructure. Reads each dirty doc and stamps it with a single field…
chronology-builder
Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…
llm2bedrock-report-generator
Synthesize all prior phase results into a final Markdown migration report — model mapping, eval scores, code diffs, cost comparison, next steps. Writes MIGRATIONREPORT .md and returns a structured report object.
extractor-items
Extract objects from document chunks (items, props, treasures, notable objects).
wiki-ingest
Processes raw sources into wiki pages. Reads source documents, synthesizes them into structured wiki pages, updates the index.