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 set-note-descriptiongit 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/set-note-description)<a href="https://agentmods.dev/skills/nweii/agent-stuff/set-note-description"><img src="https://agentmods.dev/badge/skills/nweii/agent-stuff/set-note-description/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/nweii/agent-stuff/set-note-description"><img src="https://agentmods.dev/badge/skills/nweii/agent-stuff/set-note-description.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.00043 | $0.01803 |
| Opus 5.5 | $0.00017 | $0.00721 |
| Sonnet 5.5 | $0.00009 | $0.00361 |
| Haiku 4.5 | $0.00004 | $0.00180 |
Grade A, and why
set-note-description 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 5d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Summarize frontmatter
Generate a description property for the requested notes and write it to each note’s YAML frontmatter.
Read the target vault's instructions first. For a periodic note, prefer the vault's specific rollup workflow when it covers the requested scale. For a parent period synthesized from child notes, use periodic-rollup if available. Use this skill for a note's own content, or as a fallback when no more specific workflow is available.
If no note is specified, ask which note to summarize before proceeding.
Act as a markdown file analysis assistant. Read the note and generate a description for discoverability. Either follow any specified mode or intelligently select based on content type.
Mode selection
If the user specifies a mode, use it. Otherwise, select based on content type:
Use Summary mode for
- Ephemeral content: daily logs, weekly rollups, journal entries, periodic notes
- Time-bound artifacts: meeting notes, event recaps, trip logs
- Exploratory thinking: musings, brainstorms, working-through-problems
- Personal reflections: emotional processing, retrospectives, lessons learned
These are documents where the insights or events are the value—you likely won't re-read the whole thing, you need the crystallized takeaway or memory anchor.
Use Meta mode for
- Reference material: guides, how-tos, documentation, templates
- Evergreen resources: processes, checklists, policies, standards
- Knowledge base entries: concept explanations, topic overviews
- Curated collections: link indexes, reading lists, resource compilations
- Project artifacts: specs, designs, briefs (the document serves a structural purpose)
These are documents you retrieve by need—you're searching for something that solves a problem or answers a question, not recalling what you concluded.
Evaluating the primary intent
Evaluate what the document fundamentally is (rather than looking at individual sentences to infer purpose). If signals conflict, default to the document's primary purpose:
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.
- 5d ago Changed · -1 lines 0942054fc27a
- 26d ago Changed · -9 lines · +1 tokens per session 84eadf840278
- 1mo ago First seen · 169 lines · 42 tokens per session scan A 40d77b193929
set-note-description is a skill published in the GitHub repository nweii/agent-stuff (10 stars, last pushed 3d ago), licensed MIT. It adds 43 tokens to every session and 1,803 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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.