Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/chrono-meta/forge-harnessnpx agentmods add skills/chrono-meta/forge-harness/salience-splitterWrote 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/chrono-meta/forge-harness/salience-splitter)<a href="https://agentmods.dev/skills/chrono-meta/forge-harness/salience-splitter"><img src="https://agentmods.dev/badge/skills/chrono-meta/forge-harness/salience-splitter/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/chrono-meta/forge-harness/salience-splitter"><img src="https://agentmods.dev/badge/skills/chrono-meta/forge-harness/salience-splitter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 6 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00096 | $0.04153 |
| Opus 5.5 | $0.00038 | $0.01661 |
| Sonnet 5.5 | $0.00019 | $0.00831 |
| Haiku 4.5 | $0.00010 | $0.00415 |
Grade A, and why
salience-splitter 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
salience-splitter — Governance-Semantic Context Split
Renamed from
skill-splitter(2026-07-05). Old-name references still route here. The rename reflects the generalized scope: the split criterion applies to any always-loaded context asset — a SKILL.md, a CLAUDE.md, or a memory index — not only skills. The label now names the substance (salience-tiering of always-loaded context), not one instance of it. Dogfood: applied to a memory index 2026-07-05.
An always-loaded asset that holds everything in one layer is not simple — it is unscoped. The goal is a lean always-loaded layer + an on-demand layer, not one file and its appendix.
Scope (all three share one criterion — salience: what must be in attention every load):
- SKILL.md → always-loaded SKILL.md + on-demand
SKILL_detail.md - CLAUDE.md → lean rules + on-demand detail docs (imperative
> **Detail**: See …pointers) - memory index → hot
MEMORY.md+ on-demandMEMORY_archive.md(cold/closed/superseded entries)
Trigger Phrases
| Phrase | Situation |
|---|---|
| "this skill is getting too long", "trim the skill", "split this SKILL.md" | Direct split request |
| "context-doctor flagged this skill", "SKILL.md is bloated" | Post-diagnosis split |
| "I can't see the key parts", "too much detail in the skill file" | Readability problem |
| "separate the bash from the logic", "move the templates out" | Structural refactor request |
/salience-splitter |
Explicit invocation |
Core Principle — Governance-Semantic Criterion
The split criterion is NOT length. It is: when does this content need to be in memory?
| Layer | When needed | Examples |
|---|---|---|
| SKILL.md (always-loaded) | Every invocation — session boundaries, trigger recognition, step overview, decision tables | Triggers, principles, step names + criteria, key decision tables, Done When |
| SKILL_detail.md (on-demand) | Only when executing a specific step | Bash scripts, format templates, edge cases, step-by-step execution detail |
What ships with it
1 file 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.
- 1mo ago Changed · -44 tokens per session 4b5a66a02efb
- 1mo ago First seen · 276 lines · 140 tokens per session scan A ad7596e3f887
salience-splitter is a skill published in the GitHub repository chrono-meta/forge-harness (30 stars, last pushed today), licensed MIT. It adds 96 tokens to every session and 4,153 once invoked, about $0.0004 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 skills, from other repositories
ima-skill
A general set of instructions for using a personal knowledge base and notes service to store, search, browse, and retrieve information.
mnemazina
An agent workflow that turns files and links placed in a Desktop inbox into checked, categorized notes for Obsidian, a note-taking application. It also updates section contents, a master index, and an action-oriented summary.
mnemazine-setup
A guided first-time setup for Mnemazine, a computer memory tool. It explains each step in simple language, asks one question at a time, and requests permission before installing anything.
mnemazine-update
An update tool for an installed Mnemazine setup that first shows the planned changes before editing files.
local-doc-ops
Use when extracting, inspecting, splitting, or converting local PDFs, documents, and image-based files before they enter a knowledge pipeline.
knowledge-base
A skill for managing a knowledge base through the openapi/wiki/v1 API. A knowledge base is a searchable collection of files, web pages, notes, and folders.