Memmy is a local memory hub that gives multiple AI agents one shared, persistent context about their user. It helps people continue work across agents such as Claude Code, Codex, OpenClaw, and Hermes Agent. The catalogue entries are skills for using Memmy with supported agents.
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 MemTensor/memmy-agent --skill skill-creatorgit clone --depth 1 https://github.com/MemTensor/memmy-agentWrote 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/memtensor/memmy-agent/skill-creator)<a href="https://agentmods.dev/skills/memtensor/memmy-agent/skill-creator"><img src="https://agentmods.dev/badge/skills/memtensor/memmy-agent/skill-creator/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/memtensor/memmy-agent/skill-creator"><img src="https://agentmods.dev/badge/skills/memtensor/memmy-agent/skill-creator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00028 | $0.00810 |
| Opus 5.5 | $0.00011 | $0.00324 |
| Sonnet 5.5 | $0.00006 | $0.00162 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
skill-creator 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Creator
Use this skill when creating or maintaining a memmy-agent skill.
Core Principles
Keep the skill small enough to load quickly. Put only the essential workflow in SKILL.md; move detailed reference material into references/, reusable deterministic code into scripts/, and output assets into assets/.
Write for another agent that is already capable. Include the procedural details, constraints, commands, schemas, and examples that would be annoying or risky to rediscover.
Skill Shape
A skill is a directory with one required file and optional resources:
skill-name/
├── SKILL.md
├── scripts/
├── references/
└── assets/
SKILL.md must contain YAML frontmatter followed by Markdown instructions.
Required frontmatter:
---
name: my-skill
description: Do the specific workflow. Use when the agent needs to handle concrete trigger cases.
---
Supported memmy-agent frontmatter fields:
name: lowercase letters, digits, and hyphens only.description: the trigger text that decides when the skill is useful.metadata: optional memmy-agent runtime metadata.always: optional boolean for skills that should always load.license: optional license label.allowed-tools: optional tool guidance for consumers.
Use only metadata.memmy for runtime metadata:
metadata:
memmy:
always: true
manualOnly: false
requires:
bins: ["gh"]
env: ["GITHUB_TOKEN"]
Set metadata.memmy.manualOnly: true for a Skill that must stay out of the normal Skill index and load only when the current task explicitly references $skill-name. Do not combine it with startup initialization.
Creation Workflow
- Clarify the real use cases and triggering phrases.
- Pick a short hyphen-case name.
- Create
<workspace>/skills/<skill-name>/SKILL.md. - Add only the resource directories that are actually needed.
- Run the validator.
- Test any scripts by executing them on realistic inputs.
Create files directly. There is no required init scaffold command for memmy-agent skills.
What ships with it
1 file 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.
- 1mo ago First seen · 109 lines · 28 tokens per session scan A 4f59aa343e1b
skill-creator is a skill published in the GitHub repository MemTensor/memmy-agent (2,109 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 810 once invoked, about $0.0001 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-30.
Other skills, from other repositories
browserwing-executor
Control browser automation through HTTP API. Supports page navigation, element interaction (click, type, select), data extraction, accessibility snapshot analysis, screenshot, JavaScript execution, and batch operations.
dev-browser
Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website"…
ask-user-question
Ask users questions via the UI. Use when you need clarification, user preferences, or confirmation before proceeding. The user CANNOT see CLI output - this tool is the ONLY way to communicate with them.
memos-memory-guide
Use the MemOS Local memory system to search and use the user's past conversations. Use this skill whenever the user refers to past chats, their own preferences or history, or when you need to answer from prior context. When auto-recall returns nothing (long or unclear user query), generate your own short search query…
awm-rsi-toolkit
Run AWM (Agent Workflow Memory, Wang et al. 2024) on an agent - induce reusable workflows from its successful trajectories, online over a training stream or offline from supplied experiences, then freeze the workflow memory and measure it on a published Benchmark.
browserwing-admin
Manage and operate BrowserWing — an intelligent browser automation platform. Install dependencies, configure LLM, create/manage/execute automation scripts, use AI-driven exploration to generate scripts, browse the script marketplace, and troubleshoot issues.