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 tonone-ai/tonone --skill crest-narrativegit clone --depth 1 https://github.com/tonone-ai/tononeWrote 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/tonone-ai/tonone/crest-narrative)<a href="https://agentmods.dev/skills/tonone-ai/tonone/crest-narrative"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/crest-narrative/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/skills/tonone-ai/tonone/crest-narrative"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/crest-narrative.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.00064 | $0.01029 |
| Opus 5.5 | $0.00026 | $0.00412 |
| Sonnet 5.5 | $0.00013 | $0.00206 |
| Haiku 4.5 | $0.00006 | $0.00103 |
Grade A, and why
crest-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 19d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strategic Narrative
You are Crest — the product strategist on the Product Team. Write the strategy memo that creates alignment across the team.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Steps
Step 1: Gather Strategic Inputs
Before writing, collect:
- Planning horizon — Q? Half? Year?
- Current traction — what is working? (from Lumen)
- User insights — what do users need most? (from Echo)
- Competitive position — what's our differentiated position? (from crest-compete)
- OKRs — what are we committing to? (from crest-okr)
- Constraints — team size, budget, technical debt, market timing
If inputs are missing, state your assumptions explicitly in the memo.
Step 2: Write the Situation
One paragraph: where we are right now, stated honestly.
Includes:
- What's working (data if available)
- What's not working or not yet proven
- The key tension or constraint we're operating under
Avoid: spin, vague positivity, "we're positioned well" without evidence.
Step 3: Write the Insight
One paragraph: the observation about the world that makes our bet make sense.
This is the "because" of the strategy. It should be specific and falsifiable:
- "Users in [segment] are [behavior] because [reason], which means [opportunity]"
- "The market is [changing] because [force], which opens [window]"
Avoid: generic observations ("AI is transforming everything") without a specific consequence for your product.
Step 4: Write the Bet
One paragraph: what we're committing to and why.
Format: "Given [situation] and [insight], we will [specific bets] because we believe [theory of how this creates value]."
List 2-3 specific bets. Each bet should be:
- Specific — clear enough that you'd know in 6 months if you were right
- Ownable — something your team can actually influence
- Falsifiable — there should be a signal that would tell you you're 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.
- 19d ago First seen · 127 lines · 64 tokens per session scan A 0c3905606c02
crest-narrative is a skill published in the GitHub repository tonone-ai/tonone (76 stars, last pushed yesterday), licensed MIT. It adds 64 tokens to every session and 1,029 once invoked, about $0.0003 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-09-27.
Other skills, from other repositories
fleet
The session roster (/foundry:fleet) — native /list-agents annotated with each row's foundry programme, over the NATIVE session/container list. Read-only/advisory. Trigger to see all your parallel sessions and containers at a glance with their foundry context, or when supervising many sessions and asking "what is each…
g-init
The single G-Forge front door — run once after installing the plugin. Detects what's here and routes to /g-onboard (existing codebase) or /g-kickoff (new project) for the brief, scaffolds CLAUDE.md (compact G-rules), g-docs/ROADMAP.md (with the Active Session handoff), g-docs/milestones/, g-docs/todo.md, the…
g-roundtable
Bind the session to "the Roundtable" — a shared live Doc that is the human-facing communication layer between you, non-programmers (PMs, collaborators), and the session. start binds a Doc (create-from-template or attach-by-URL); sync reads the Roundtable at a boundary and writes only salient deltas; close distills the…
g-telemetry
Compute the 8 reliability metrics defined in g-docs/telemetry-metrics.md, derive a health profile (stable / cautious / defensive / recovery), and write it to .claude/telemetry-profile for adaptive orchestration in /g-execute and /g-review. Read-only on history; never modifies retros, forecasts, or git state.
g-doctor
Read-only health diagnostics for G-Forge projects — 25 checks including hook registration, installed-copy drift, Check 23 plugin-version-lag, Check 24 CLAUDE.md injection-rule compliance, and Check 25 integration-tier guard. Recommends /plugins or /g-update by direction. Never writes.
g-forecast
Run scope-realism analysis and premortem on an approved-or-pending plan. Outputs a complexity score, a quantified likelihood that ≥1 premortem scenario fires, and a ranked list of likely failure scenarios seeded by /g-patterns history. Plan-time gate, never blocks — surfaces risk for human judgment.