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/foliveira/harmonia/remembernpx skills add foliveira/harmonia --skill remembergit clone --depth 1 https://github.com/foliveira/harmoniaWhat 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.00029 | $0.00265 |
| Opus 5 | $0.00015 | $0.00133 |
| Sonnet 5 | $0.00006 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
remember 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 2d 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.
What it actually says
Capture ONE learning through the memory script with an explicit tier. Never a bare or defaulted global write.
-
Elicit the tier from the developer - do not guess it:
project- specific to this repo (the usual choice);global- a cross-project pattern, carrying NO client content. Ask which tier, and pass--clientfor a client-work learning.
-
Capture it, body on stdin:
echo "<the learning body>" | bash ${CLAUDE_PLUGIN_ROOT}/bin/memory/capture.sh --tier <project|global> [--client] --title "<short title>" --tags "<lang,topic>"
Client content never reaches the global tier (R21): capture.sh refuses a --client write to --tier global with a non-zero exit, and refuses a global entry with no recognized language tag (it would be unreachable by recall). That deterministic guard is the backstop behind the tier you elicit - not a licence to default the tier. Surface the script's output.
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.
- 2d ago First seen · 21 lines · 29 tokens per session scan A c1a9b3fda224
remember is a skill published in the GitHub repository foliveira/harmonia (2 stars, last pushed 17d ago), licensed MIT. It adds 29 tokens to every session and 265 once invoked, about $0.0001 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
serphouse-api
Teach AI agents to call SERPHouse REST APIs with curl for web search, SERP data, and SEO intelligence.
serphouse-nodejs
Teach AI agents to use @serphouse/serphouse-nodejs SDK for typed SERP data access.
serphouse-mcp
Teach AI agents to use SERPHouse MCP tools for live SERP data, Google verticals, and SEO intelligence.
explaining-code
Explains code with visual diagrams and analogies. Use when explaining how code works, teaching about a codebase, or when the user asks "how does this work?".
teach-impeccable
One-time setup that gathers design context for your project and saves it to your AI config file. Run once to establish persistent design guidelines.
alego-doc-standards
Use when writing, moving, reviewing, or auditing documentation in the alego repo — choosing hierarchy and detail, separating tutorials from references, checking tutorial progression, trimming doc slop, responding to a verify-doc-budgets failure, or requests like "improve the docs", "audit the docs", "where should this…