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/eric-cielo/moflo/memory-teamnpx skills add eric-cielo/moflo --skill memory-teamgit clone --depth 1 https://github.com/eric-cielo/mofloWrote 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/eric-cielo/moflo/memory-team)<a href="https://agentmods.dev/skills/eric-cielo/moflo/memory-team"><img src="https://agentmods.dev/badge/skills/eric-cielo/moflo/memory-team.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.00126 | $0.01783 |
| Opus 5 | $0.00063 | $0.00892 |
| Sonnet 5 | $0.00025 | $0.00357 |
| Haiku 4.5 | $0.00013 | $0.00178 |
Grade A, and why
memory-team 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 4d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/memory-team — Share Learnings via a Git-Tracked Artifact
Wires up memory.team_artifact: a diffable JSONL file (.moflo/shared/learnings.jsonl) that lives
in the repo, reviewed like any other change. Teammates git pull it and their next session
auto-imports the merged learnings; each entry is stamped with its git author. This skill also installs a
pre-commit hook so the artifact is re-exported and staged on every commit — the learnings ride along
in each PR with zero effort.
One mechanism, two audiences. A team and one person across machines are the same problem — push the durable slice through git. This skill covers both; the only difference is whether anyone else is on the other end. (Prefer a private, non-git file for your own machines? See "Advanced" at the bottom —
flo memory syncmoves a binary artifact that keeps embeddings verbatim.)
Arguments: $ARGUMENTS — pass --solo to skip team-oriented wording (still identical setup).
When to use
- "share learnings / memory with my team"
- "commit our moflo knowledge to the repo"
- "sync memory between my laptop and desktop"
- "auto-export the learnings on every PR / commit"
- "set up
team_artifact"
For many worktrees on one machine, that's a shared local store, not git — use /memory-worktree.
Procedure
Step 0 — Memory first (gate requirement)
mcp__moflo__memory_search { query: "team_artifact learnings jsonl git share import session-start", namespace: "guidance" }
Step 1 — Confirm this is the git path
- Team on one repo, or one person across machines who both push to the same repo? → correct skill.
- Many worktrees on one machine, no cross-machine need? → redirect to
/memory-worktree. - A private synced file (Dropbox/USB), no git? → point at the Advanced section (
flo memory sync).
Step 2 — Set the config
Read the project-root moflo.yaml and add/merge under memory: — preserve existing keys:
memory:
team_artifact: .moflo/shared/learnings.jsonl
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.
- 4d ago First seen · 165 lines · 126 tokens per session scan A 21cde0fd4554
memory-team is a skill published in the GitHub repository eric-cielo/moflo (18 stars, last pushed 6d ago), licensed MIT. It adds 126 tokens to every session and 1,783 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-30.
Other skills, from other repositories
handoff
Write a compact, decision-ready handoff so the next session (or the user) can continue without reconstructing the current one. Use when the session is ending, context is running low, the user asks for a handoff / "pass the baton" / "hand off", or a long-running operation needs a durable state checkpoint.
cao-learning
Report task outcomes and distill lessons so the team improves across runs — reportoutcome after each unit of work, retrospector handoffs at natural boundaries, and applying injected lessons. Use in workflows that run repeatedly over similar work items. Requires memory.learningenabled; degrade silently when the tools…
context-management
Project context loading, isolation, and persistent state management across CCPM sessions.
archon
Autonomous multi-session campaign agent. Decomposes large work into phases, delegates to sub-agents, reviews output, and maintains campaign state across context windows. Use for work that spans multiple sessions and needs persistent state, quality judgment, and strategic decomposition.
marshal
Meta-orchestrator that takes any direction — broad, specific, or vague — and autonomously chains skills and context into actionable work. Gathers context from codebase, docs, and memory. Only asks the user when it genuinely cannot proceed. Single-session orchestrator.
wiki
Markdown-first knowledge base where the LLM acts as librarian. Ingests raw sources, compiles and interlinks topic files, self-maintains an index. No vector DB or embeddings required -- uses LLM-native navigation over structured markdown up to 400K words.