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 agentmods add skills/robinslange/learning-loop/harvestnpx skills add robinslange/learning-loop --skill harvestgit clone --depth 1 https://github.com/robinslange/learning-loopWrote 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/robinslange/learning-loop/harvest)<a href="https://agentmods.dev/skills/robinslange/learning-loop/harvest"><img src="https://agentmods.dev/badge/skills/robinslange/learning-loop/harvest.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 | $0.00086 | $0.01355 |
| Opus 5 | $0.00043 | $0.00678 |
| Sonnet 5 | $0.00017 | $0.00271 |
| Haiku 4.5 | $0.00009 | $0.00136 |
Grade A, and why
harvest 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 3d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harvest portable insights
Collects notes/memories marked portable: true, scrubs them against this instance's IP deny-list, lets you review survivors, and emits a harvest-bundle-<date>/ to carry home and absorb with /learning-loop:ingest bundle <path>.
Invariants (do not violate)
- Whitelist only: only
portable: true. Never harvest byvisibility, tag, or inference. The gate matches the exact literal lowercasetrue—portable: True,yes, or1are silently excluded (fail-closed, no leak), so if an operator expected a note to carry and it didn't, check the marker is exactlyportable: true. - Mechanical gate: the deny-list block is authoritative. You may drop MORE in review; you may never un-block or add a note the gate excluded.
Paths
Resolve PLUGIN_DATA, VAULT, and the plugin root per ${CLAUDE_PLUGIN_ROOT}/skills-shared/paths-preamble.md (read it and apply). The deny-list file and dedup log are resolved mechanically, NOT hardcoded:
- deny-list:
node -e "import('${CLAUDE_PLUGIN_ROOT}/scripts/lib/paths.mjs').then(m=>console.log(m.DATA_FILES.harvestDenylist(process.argv[1])))" PLUGIN_DATA - dedup log: same with
DATA_FILES.harvestedLog. The memory dir:node -e "import('${CLAUDE_PLUGIN_ROOT}/scripts/lib/memory-paths.mjs').then(m=>console.log(m.resolveMemoryDir(process.env.CLAUDE_PROJECT_DIR)))".
Process
1. Collect (mechanical whitelist)
Pass DIRECTORIES — the script walks them; do not enumerate files yourself:
node ${CLAUDE_PLUGIN_ROOT}/scripts/harvest-collect.mjs "<VAULT>" "<memDir>"
prints the paths with portable: true. These are the ONLY candidates. Capture them to a temp file for the next steps.
2. Dedup
node ${CLAUDE_PLUGIN_ROOT}/scripts/harvest-dedup.mjs "<dedupLog>" [--all] < candidates.txt
(CLI reads candidate paths on stdin, one per line; --all ignores the log.) Use the printed filtered list going forward.
3. Federation guard (mechanical, warn-not-block)
node ${CLAUDE_PLUGIN_ROOT}/scripts/federation-active.mjs "<PLUGIN_DATA>"
If it prints FEDERATED, show this before review: "⚠ this instance is federated — confirm each note is yours to carry, not company IP." Friction, not a block.
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.
- 3d ago First seen · 69 lines · 86 tokens per session scan A 3bf7f2e2eb67
harvest is a skill published in the GitHub repository robinslange/learning-loop (11 stars, last pushed 12d ago), licensed Apache-2.0. It adds 86 tokens to every session and 1,355 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…