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 shennawardana23/skillme --skill continuous-learning-v2git clone --depth 1 https://github.com/shennawardana23/skillmeWrote 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/shennawardana23/skillme/continuous-learning-v2)<a href="https://agentmods.dev/skills/shennawardana23/skillme/continuous-learning-v2"><img src="https://agentmods.dev/badge/skills/shennawardana23/skillme/continuous-learning-v2/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/shennawardana23/skillme/continuous-learning-v2"><img src="https://agentmods.dev/badge/skills/shennawardana23/skillme/continuous-learning-v2.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.00123 | $0.01611 |
| Opus 5 | $0.00062 | $0.00805 |
| Sonnet 5 | $0.00025 | $0.00322 |
| Haiku 4.5 | $0.00012 | $0.00161 |
Grade A, and why
continuous-learning-v2 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 10d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Continuous Learning v2 (instinct-based)
A finer-grained alternative to continuous-learning: instead of
evaluating a whole session once at the end and writing out full skill
files, this approach observes every tool call via hooks and accumulates
small, atomic, confidence-scored "instincts" that later get clustered
into skills, commands, or agents. See continuous-learning for when the
simpler whole-session approach is enough — don't reach for this added
complexity unless you actually need per-behavior confidence tracking or
project/global separation.
Why hooks instead of a Stop hook
A Stop hook only fires once, on sessions that end normally, and only
gets one pass over the whole transcript. PreToolUse/PostToolUse hooks
fire on every single tool call, deterministically — so no candidate
pattern is missed because the session ended unusually, and observation
happens incrementally rather than in one large end-of-session pass.
The instinct model
An instinct is one atomic, learned behavior — one trigger, one action — not a full skill:
---
id: prefer-explicit-error-returns
trigger: "when writing a function that can fail"
confidence: 0.7
domain: "code-style"
source: "session-observation"
scope: project
project_id: "a1b2c3d4e5f6"
---
# Prefer Explicit Error Returns
## Action
Return an explicit error value rather than panicking, for any function
whose failure is an expected, recoverable condition.
## Evidence
- User corrected a panic-based approach to an error-return approach twice
- Pattern held across three subsequent sessions without correction
Properties that make this different from a whole extracted skill:
- Atomic — one trigger, one action, easy to evaluate independently
- Confidence-weighted — a number, not a boolean, that can move up or down as evidence accumulates
- Domain-tagged —
code-style,testing,git,debugging, etc. - Evidence-backed — records what observations produced it, so a human reviewing it later can see why it exists
- Scope-aware —
projectby default, promotable toglobal
What ships with it
2 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.
- 10d ago First seen · 161 lines · 123 tokens per session scan A 1c1088d71ecb
continuous-learning-v2 is a skill published in the GitHub repository shennawardana23/skillme (2 stars, last pushed 12d ago), licensed Apache-2.0. It adds 123 tokens to every session and 1,611 once invoked, about $0.0006 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
persistent-memory
Persists context across conversations as plain markdown so every future session can enrich a topic-scoped memory (e.g. parenting, relationship-anna, work-history, project-acme). Four operations: write (extract candidates, resolve as ADD / UPDATE / DELETE / NOOP per Mem0), read (load a ≤ 200-line INDEX; fetch detail…
opencode-memory
Browse local OpenCode history: sessions, messages, plans, prompt history, and prior decisions. Use when the user says history, previous session, last time, remember, recall, plans, prior work, or when resuming/debugging repeated work where earlier OpenCode context may help. Do not use for fresh tasks or when current…
learn-from-experience
Learn from experience: self-reflection + self-criticism + self-learning + self-organizing memory + cross-session sync. Agent evaluates its own work, catches mistakes, and improves permanently. Compiles confirmed learnings to global config for automatic cross-session persistence. Use when (1) a command, tool, API, or…
memory-integration
Use to maintain context across sessions - integrates episodic-memory for conversation recall and mcpmemory knowledge graph for persistent facts.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.