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 skills add Muuuun/luxas --skill narrativegit clone --depth 1 https://github.com/Muuuun/luxasWrote 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/skills/muuuun/luxas/narrative)<a href="https://agentmods.dev/skills/muuuun/luxas/narrative"><img src="https://agentmods.dev/badge/skills/muuuun/luxas/narrative.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00045 | $0.01308 |
| Opus 5 | $0.00023 | $0.00654 |
| Sonnet 5 | $0.00009 | $0.00262 |
| Haiku 4.5 | $0.00005 | $0.00131 |
Grade A, and why
narrative 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 8d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Narrative Skill
Two jobs, in order of importance:
- Revision protocol — how to absorb PI/user feedback without the report degrading back into a patchwork (most narrative damage happens during feedback rounds, not first drafts).
- Article-type templates — positive examples of section logic per article type, consumed at outline time.
This skill is the delta on top of brain.md's <report_synthesis_protocol>
(outline-first, claims-as-titles, lab-book test, anti-stacking pass). It does
not repeat those rules — it adds what they lack: per-type section logic, the
figure-narrative binding, and what to do when feedback arrives.
First draft (thin — most rules live in brain.md)
- Pick the article type and record it as the first line of
notes/report_outline.md:type: empirical | feasibility | comparison | policy-zh | survey. Surveys: stop here and followskills/review/+skills/survey-methodology/instead — never both pipelines. - Read
templates/<type>.mdBEFORE writing the outline. The template gives the section logic for that type; your outline instantiates it with this project's claims. The lab-book test catches structure that mirrors the experiment DAG; the template shows what to write instead. - Read
references/figure_narrative.mdbefore commissioning figures. The outline must name its Figure 1 (schematic) and its hero figure (the one figure that settles the central claim) — both are outline-level decisions, not afterthoughts.
Revision protocol (core)
Every feedback batch that touches the report gets classified BEFORE any
edit. Mixed batches: tag every item first, edit second (tag-all-before-
edit-any) — append-only reviews/pi_feedback.md means earlier instructions
never vanish, so there is no need to rush.
Add the class tag to each checklist line in notes/memory.md (the existing
pi_correction_protocol checklist — same boxes, one tag + one-line rationale
extra):
- [ ] <instruction verbatim> [class: local-fix | section-rewrite | restructure — <one-line why>]
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 120 lines · 45 tokens per session scan A d03d4002680d
narrative is a skill published in the GitHub repository Muuuun/luxas (975 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 1,308 once invoked, about $0.0002 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-30.
Other skills, from other repositories
forecasting
Superforecasting with calibrated reasoning, Brier score tracking, and prediction ledger management.
aws-fde-delivery
Forward Deployed Engineer delivery contract for AWS engagements, build-first artifacts, grounded cost estimates, Well-Architected review, evolution roadmap.
evaluate
Evaluate technologies and competitive developments against Genesis architecture.
integrate-module
Turn any external program into a Genesis module via structured discovery, connection mapping, config generation, and verification.
lead-generation
Prospect discovery, enrichment, scoring, and reporting against an Ideal Customer Profile.
osint
OSINT investigation — discover, track, and report on people, companies, and technologies.