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 yogasw/wick --skill wick-notesgit clone --depth 1 https://github.com/yogasw/wickWrote 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/yogasw/wick/wick-notes)<a href="https://agentmods.dev/skills/yogasw/wick/wick-notes"><img src="https://agentmods.dev/badge/skills/yogasw/wick/wick-notes/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/yogasw/wick/wick-notes"><img src="https://agentmods.dev/badge/skills/yogasw/wick/wick-notes.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.00084 | $0.00895 |
| Opus 5.5 | $0.00034 | $0.00358 |
| Sonnet 5.5 | $0.00017 | $0.00179 |
| Haiku 4.5 | $0.00008 | $0.00089 |
Grade A, and why
wick-notes 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Notes
Notes are the running record of what has been learned about a piece of work: findings, decisions, dead ends, and what to do next. They outlive the conversation that produced them, which is what lets a fresh session pick up where a derailed one left off.
Use the notes connector. It works with or without a ticket — a session
attached to a ticket reads and writes the ticket's notes (shared with every
other session on it); a session attached to nothing keeps its own.
Read them before you work
Your prompt tells you how many notes are waiting. The bodies are not in your prompt — deliberately, because a long-lived ticket would otherwise charge its whole history on every turn.
So when the pointer says there are notes and you are about to do real work rather than answer a passing question:
notes_list
No arguments needed: the scope defaults to this session, which resolves to the ticket's notes when it belongs to one. Reading them is cheaper than rediscovering what they say, and much cheaper than contradicting it.
Write one when you learn something
The test: would a later session, or a person, have to work this out again? If yes, write it down.
notes_add body="Retries fire every 30s because the queue re-enqueues on 5xx.
The 401 comes from the token refresh, not the webhook itself."
Worth a note: a root cause, a ruled-out hypothesis, a decision and why, a constraint you discovered, what you would do next, or a warning that a path leads nowhere. Not worth a note: a summary of what you just said in chat, or anything already obvious from the code.
Write one before handing off, and before saying a fresh session should take over — that is the moment the note is worth the most.
Checkable notes
For something with a done state, make it checkable and close it when it is done:
notes_add body="Confirm the fix on staging" checkable=true
notes_check note_id=<id> done=true
This is not a todo list with deadlines. It is a note that happens to have a box, so a reader can see what has and has not been confirmed.
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 · 103 lines · 84 tokens per session scan A 09f102a45019
wick-notes is a skill published in the GitHub repository yogasw/wick (3 stars, last pushed yesterday), licensed MIT. It adds 84 tokens to every session and 895 once invoked, about $0.0003 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
mnemon
Persistent memory CLI for LLM agents. Store facts, recall past knowledge, link related memories, manage lifecycle.
mnemon
Persistent memory CLI for LLM agents. Store facts, recall past knowledge, link related memories, manage lifecycle.
mnemon
Persistent memory CLI for Hermes Agent. Store facts, recall past knowledge, link related memories, manage lifecycle.
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
alive:mine-for-context
Deep context extraction from source material. Creates reference bundles, builds extraction plans, tracks what's been extracted, and discovers new targets — people, subjects, patterns, connections. The archaeologist that turns raw sources into structured knowledge. Can be invoked by alive:session-history for targeted…
session-search
Find context from past Claude Code (CLI) and Claude Cowork (desktop) sessions on this Mac. Use when the user wants to recall something they did before but can't find it , phrasings like "where did I work on X", "find that session where I…", "when did I last do Y", "pull up the conversation about Z", "that time I…