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 nweii/agent-stuff --skill clip-skillsgit clone --depth 1 https://github.com/nweii/agent-stuffWrote 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/nweii/agent-stuff/clip-skills)<a href="https://agentmods.dev/skills/nweii/agent-stuff/clip-skills"><img src="https://agentmods.dev/badge/skills/nweii/agent-stuff/clip-skills.svg" alt="Measured on agentmods" 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.00082 | $0.01069 |
| Opus 5 | $0.00041 | $0.00535 |
| Sonnet 5 | $0.00016 | $0.00214 |
| Haiku 4.5 | $0.00008 | $0.00107 |
Grade A, and why
clip-skills 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 7d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clip skills
Turn a bunx skills manifest (run in the terminal, not the browser) into one note in 03-Records/Snippets/Repos/. This is the CLI-entry twin of the Obsidian Web Clipper "Agent skills" template, which handles the same note when clipping a GitHub/skills.sh page in the browser. Match that template's shape so notes from either path look identical.
Defer first
Vault layout, metadata semantics, and tool-choice rules live in the vault's AGENTS.md / CLAUDE.md. Read those if unsure about a field or which write tool to use. This skill only adds the procedure for this one note type.
Input
The user has run one of these and pasted the output:
bunx skills add <owner/repo or URL> -l # lists a collection's skills
bunx skills use <owner/repo> --skill <name>
Derive <owner/repo> (or the bare URL slug, e.g. https://docs.stripe.com) from what they ran. If the listing is missing or partial, ask them to re-run with -l.
Note shape
Path: 03-Records/Snippets/Repos/
Filename:
- Collection of skills →
<1-3 word descriptor> skills - <repo owner>(e.g.Payments skills - stripe,Design engineering skills - Emil Kowalski) - Single skill →
<1-4 word descriptor of what it does> skill - <repo owner>
No quotes in the filename.
Frontmatter:
aliases: # 1-2 retrieval-friendly alt titles, sentence case
categories: # [[Snippets]] and [[Web]] always; add [[Clippings]] ONLY if the source is a clipped web page (e.g. a docs site), not a bare GitHub repo
icon: "LiSparkles"
description: # what this offers in 1-2 plain sentences — collection focus/breadth, or the single skill's own description lightly compressed
url: # the source page/repo URL, query string stripped
author: # repo owner or credited person as a [[wikilink]]; prefer full name over handle
last: # today's date
tags: # clippings/skills, plus 1-2 broad lowercase topical tags (hyphens, no spaces)
Body — two sections:
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.
- 7d ago First seen · 95 lines · 82 tokens per session scan A 638300694bda
clip-skills is a skill published in the GitHub repository nweii/agent-stuff (9 stars, last pushed 19d ago), licensed MIT. It adds 82 tokens to every session and 1,069 once invoked, about $0.0004 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
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…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.