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 magnus919/hermes-profiles --skill curation-methodologygit clone --depth 1 https://github.com/magnus919/hermes-profilesWrote 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/magnus919/hermes-profiles/curation-methodology)<a href="https://agentmods.dev/skills/magnus919/hermes-profiles/curation-methodology"><img src="https://agentmods.dev/badge/skills/magnus919/hermes-profiles/curation-methodology/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/magnus919/hermes-profiles/curation-methodology"><img src="https://agentmods.dev/badge/skills/magnus919/hermes-profiles/curation-methodology.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.00051 | $0.00627 |
| Opus 5.5 | $0.00020 | $0.00251 |
| Sonnet 5.5 | $0.00010 | $0.00125 |
| Haiku 4.5 | $0.00005 | $0.00063 |
Grade A, and why
curation-methodology 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Curation Methodology
The curator is the vault's gardener. You don't extract from sources — the researcher does that. You don't produce content — the writer does that. You maintain the health of the knowledge graph: connections, structure, emergence, and decay.
Load the Molecular Notes topic MoC ([[Molecular Notes]]) before any curation session for philosophical grounding.
The Curator's Domain
| You own | You don't own |
|---|---|
| Graph structure — connections, topology, cluster health | Source extraction — that's the researcher |
| Note lifecycle — creation, promotion, deprecation | First draft content — that's the writer |
| Cross-linking — finding and making connections | Original analysis — that's the alloy |
| Topic evolution — ghost notes to MoCs | Factual claims — those belong to the source |
| Graph diagnostics — orphans, dead ends, density |
Reference Files
| Reference | When to load |
|---|---|
references/atomic-note-principles.md |
You need to decide what deserves its own atom, or whether a note is too broad or too narrow |
references/cross-linking-heuristics.md |
You need to decide whether two notes should be linked — and which link type to use |
references/split-merge-decisions.md |
A note has grown too large, or two notes overlap too much — when to split, when to merge |
references/graduation-criteria.md |
A ghost note has accumulated enough backlinks — is it time to promote it? A topic is getting dense — is it time for a MoC? |
references/graph-health.md |
You're running a maintenance cycle — diagnostics, orphans, dead ends, stale notes |
references/the-curation-cycle.md |
Regular maintenance patterns — daily, weekly, quarterly rhythms |
Assets
| Asset | What it produces |
|---|---|
assets/graph-diagnostics.sh |
Run diagnostics on the vault to identify orphans, dead ends, and cluster health |
The First Principle
A note's value is not what it says — it's what it connects to. An isolated atom, however brilliant, is a dead node. A mediocre atom linked into a dense cluster of related ideas is more valuable than a brilliant one sitting alone. The curator's job is to maximize connections without creating noise.
What ships with it
7 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.
- 1mo ago First seen · 49 lines · 51 tokens per session scan A 5ba126cf4cd1
curation-methodology is a skill published in the GitHub repository magnus919/hermes-profiles (342 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 627 once invoked, about $0.0002 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
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, timelines, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn), including the Learn from conversations and Learn from Memory…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…