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 serudda/fragments-vault --skill organize-fragmentsgit clone --depth 1 https://github.com/serudda/fragments-vaultWrote 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/serudda/fragments-vault/organize-fragments)<a href="https://agentmods.dev/skills/serudda/fragments-vault/organize-fragments"><img src="https://agentmods.dev/badge/skills/serudda/fragments-vault/organize-fragments/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/serudda/fragments-vault/organize-fragments"><img src="https://agentmods.dev/badge/skills/serudda/fragments-vault/organize-fragments.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.00056 | $0.00536 |
| Opus 5 | $0.00028 | $0.00268 |
| Sonnet 5 | $0.00011 | $0.00107 |
| Haiku 4.5 | $0.00006 | $0.00054 |
Grade A, and why
organize-fragments 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 12d 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.
What it actually says
Organize Fragments
Role
You are a fragment organizer. Move fragments from inbox to their permanent category.
Principles
- Fast decisions - Show, suggest, move. No friction.
- Smart suggestions - Use tags to suggest the right category
- Skip is valid - Not everything needs to be categorized today
- No editing - Editing was done in save-fragment. This is just sorting.
Flow
Step 1: Read Inbox
Read fragments/inbox.md.
If empty: "Inbox is empty. Nothing to process." — End.
Step 2: Show Summary
You have X fragments in inbox:
1. "First line..." → #tag1 #tag2
2. "First line..." → #tag1 #tag2
Process all or select some?
Step 3: For Each Fragment
Show it:
───────────────────────────────────
> "Fragment text"
**Source**: Author, Platform
**Tags**: #tag1 #tag2
**Why**: Reason
**Date**: YYYY-MM-DD
───────────────────────────────────
Suggest category based on tags:
I suggest: **building.md** (because of #build-in-public)
1. ✓ Move to building.md
2. → Another category
3. ⏭ Skip
4. ✕ Delete
Handle response:
- "1" / "yes" / category name → Move there
- "2" / "other" → Ask which
- "3" / "skip" → Leave in inbox
- "4" / "delete" → Delete from inbox
Step 4: Execute Move
- Append fragment to destination file
- Remove from inbox.md
- Confirm: "Moved to building.md ✓"
Step 5: Final Summary
Organized: X fragments
- 2 → building.md
- 1 → deleted
Y remaining in inbox.
New Category
If user wants a category that doesn't exist:
- Confirm creation
- Create the file with header
- Update CLAUDE.md structure
- Move fragment there
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.
- 12d ago First seen · 101 lines · 56 tokens per session scan A f61f13ec0149
organize-fragments is a skill published in the GitHub repository serudda/fragments-vault (6 stars, last pushed 7mo ago), licensed MIT. It adds 56 tokens to every session and 536 once invoked, about $0.0003 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 skills, from other repositories
update-turbo
Update installed Turbo skills from the local repo with a dynamic changelog, conflict resolution for customized skills, and guided user experience. Use when the user asks to "update turbo", "update turbo skills", "reinstall turbo", or "upgrade turbo".
mm-resume
A workflow for restoring project context after starting a new Claude Code session or clearing the conversation. It reads project notes, recent session information, version-control status, and available planning files.
mm-setup
A setup guide that personalizes a shared mm system for one user. It asks for details such as your name, work area, tools, language, and Obsidian vault location, then saves them in private configuration files.
mm
A dispatcher that provides short /mm commands for project setup, session recovery, project overviews, and workflow checks. It maps these aliases to longer system commands.
file-organization
Use when organizing, deduplicating, or cleaning up files. Covers safe classification and renaming, finding true duplicates, reclaiming space, and never destroying data during a cleanup.
apple-shortcuts
Generate importable Apple Shortcuts (.shortcut / plist XML) for macOS and iOS. Use this skill whenever the user wants to create, modify, reverse-engineer, or understand Apple Shortcuts, including native actions, third-party app integrations (Actions, Data Jar, Toolbox Pro, Scriptable, a-Shell, Jayson, Pushcut)…