harvester-memory-sync

harvester-memory-sync is a skill for Claude Code, Codex from humanerd-drew/opencode-drewgent. It costs 0 tokens per session (837 once invoked), scanned A, original, MIT.

A synchronization guide that copies analyzed trend results from a growth system into a long-term memory system. It defines which scored trends go to monthly insights, pending reviews, or saved concepts.

In plain words
What is it for?
Use it after a trend-harvesting job or on demand to sync retained trends, review candidates, approved concepts, and applied trends between the two project areas.
Why use it?
It prevents useful trend analysis from remaining isolated in the collection system and keeps approved results available in long-term memory.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 scripts/harvester_memory_sync.py.

Good fit Use it after a trend-harvesting job or on demand to sync retained trends, review candidates, approved concepts, and applied trends between the two project areas.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/humanerd-drew/opencode-drewgent
agentmods
npx agentmods add skills/humanerd-drew/opencode-drewgent/harvester-memory-sync

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for harvester-memory-sync

README.md
[![agentmods](https://agentmods.dev/badge/skills/humanerd-drew/opencode-drewgent/harvester-memory-sync/github.svg)](https://agentmods.dev/skills/humanerd-drew/opencode-drewgent/harvester-memory-sync)
Your own site
<a href="https://agentmods.dev/skills/humanerd-drew/opencode-drewgent/harvester-memory-sync"><img src="https://agentmods.dev/badge/skills/humanerd-drew/opencode-drewgent/harvester-memory-sync/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.

agentmods 80×15 button for harvester-memory-sync

Your own site · 80×15
<a href="https://agentmods.dev/skills/humanerd-drew/opencode-drewgent/harvester-memory-sync"><img src="https://agentmods.dev/badge/skills/humanerd-drew/opencode-drewgent/harvester-memory-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 837 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00837
Opus 5.5 $0.00000 $0.00335
Sonnet 5.5 $0.00000 $0.00167
Haiku 4.5 $0.00000 $0.00084

Measured 1mo ago against content hash b0e71eb77431, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

harvester-memory-sync 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.

@action/skills/brain/harvester-memory-sync/SKILL.md · 93 lines

How it starts

The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Harvester Memory Sync — P4→P2 Bridge

Purpose

Sync trend-harvester's analyzed trends to P2-hippocampus long-term memory. Keeps P2-hippocampus/memories/insights/ in sync with P4-cortex/growth/trend-harvester/ analyzed output.

This closes the P4→P2 downstream flow: trend-harvester output must reach P2-hippocampus/memories/ so the full memory layer benefits from growth insights.

Trigger

  • Primary: Run automatically after trend-harvester-001 job completes
  • Fallback: Run on-demand via python3 scripts/harvester_memory_sync.py

Data Flow

P4-cortex/growth/trend-harvester/
  collected/     ← raw data (NOT synced)
  analyzed/      ← scored trends → COPY to P2 memories
    keep/        ← score ≥ 6.0 → insights/YYYY-MM.md
    review/      ← 4.0 ≤ score < 6.0 → insights/pending/
    graveyard/   ← NOT synced
  pending/       ← approved trends → concepts/
  applied/       ← applied trends → concepts/ + notes

P2-hippocampus/memories/
  insights/      ← trend insights (by date)
  concepts/      ← applied concept files

Sync Rules

Source (P4) Destination (P2) Action
analyzed/keep/*.json insights/YYYY-MM.md Append to monthly insight
analyzed/review/*.json insights/pending/ Create pending insight file
analyzed/graveyard/*.json — Skip (no sync)
pending/*.json concepts/ Create/update concept file
applied/*.json concepts/ Create/update concept + tag trend-applied

Anti-Duplication

  • Use content hash (MD5 of trend URL or description) as dedup key
  • Check if same hash already exists in target before writing
  • Track synced hashes in {{AGENT_NAME_LOWER}}_hidden_state.json["harvester_synced_hashes"]

State Tracking

Read/write from P4-cortex/knowledge/{{AGENT_NAME_LOWER}}_hidden_state.json:

{
  "harvester_synced_hashes": ["hash1", "hash2"],
  "last_sync_at": "2026-05-12T10:00:00+09:00",
  "last_sync_job": "trend-harvester-001",
  "synced_count": 42
}

Read the full file on GitHub · 93 lines

Changes

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.

  1. 1mo ago First seen · 93 lines · 0 tokens per session scan A b0e71eb77431

Subscribe to this mod's changes

harvester-memory-sync is a skill published in the GitHub repository humanerd-drew/opencode-drewgent (3 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 837 tokens. 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.

Related

Other skills, from other repositories

mem0-oss-to-platform

Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…

mem0ai/mem0 · 217 tokens

forget

Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…

asgeirtj/system_prompts_leaks · 74 tokens

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…

danielmiessler/LifeOS · 196 tokens

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.

opensquilla/opensquilla · 44 tokens

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…

shiwenwen/hope-agent · 115 tokens

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.

GanyuanRan/Aegis · 45 tokens