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/chachamaru127/codex-harness/sync-ssot-from-memorynpx skills add Chachamaru127/codex-harness --skill sync-ssot-from-memorygit clone --depth 1 https://github.com/Chachamaru127/codex-harnessWrote 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/chachamaru127/codex-harness/sync-ssot-from-memory)<a href="https://agentmods.dev/skills/chachamaru127/codex-harness/sync-ssot-from-memory"><img src="https://agentmods.dev/badge/skills/chachamaru127/codex-harness/sync-ssot-from-memory.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.1 | $0.00070 | $0.00843 |
| Opus 5 | $0.00035 | $0.00421 |
| Sonnet 5 | $0.00014 | $0.00169 |
| Haiku 4.5 | $0.00007 | $0.00084 |
Grade A, and why
sync-ssot-from-memory 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 5d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync SSOT from Memory
Promote important observations recorded in memory systems (Claude-mem or Serena) to the project's SSOT:
.claude/memory/decisions.md and .claude/memory/patterns.md.
Quick Reference
- "Save what we learned for next time" → this skill
- "Promote important decisions to SSOT" → this skill
- "Organize decisions (why) and methods (how) separately" → Reflect in decisions/patterns separately
Supported Memory Systems
| System | Detection | How to Get Observations |
|---|---|---|
| Claude-mem | ~/.claude-mem/settings.json |
mcp__plugin_claude-mem_mcp-search__search |
| Serena | .serena/memories/ |
mcp__serena__read_memory |
Auto-detected at execution, using available system.
Execution Flow
Step 0: Detect Memory System
# Claude-mem check
if [ -f "$HOME/.claude-mem/settings.json" ]; then
MEMORY_SYSTEM="claude-mem"
fi
# Serena check
if [ -d ".serena/memories" ]; then
MEMORY_SYSTEM="serena"
fi
Step 1: Extract SSOT Promotion Candidates
For Claude-mem:
- Search for
type:decision - Search for
type:discovery concepts:pattern - Search for
type:bugfix concepts:gotcha
For Serena:
- List and read relevant memories
Step 2: Filter by Promotion Criteria
Decisions Candidates (Why) → decisions.md:
- Technology selection reasons
- Guardrail reasons
- User requirements/constraints
Patterns Candidates (How) → patterns.md:
- Recurrence prevention (bugfixes)
- Reusable solutions
- Implementation patterns
Exclusions:
- Work-in-progress rough notes
- Personal/confidential information
- One-time tasks (not reusable)
Step 3: Reflect to SSOT
Add entries to decisions.md and patterns.md with:
- Unique ID (D{N} or P{N})
- Date, Tags, Observation ID
- Structured content (Conclusion, Background, Options, etc.)
Step 4: Output Summary
## SSOT Promotion Results
### Added/Updated
| File | Item | Observation ID |
|------|------|----------------|
| decisions.md | D{N}: {Title} | #{id} |
| patterns.md | P{N}: {Title} | #{id} |
### Excluded
- Work-in-progress: N items
- Duplicates: N items
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.
- 5d ago First seen · 99 lines · 70 tokens per session scan A 4878fa4f9c6c
sync-ssot-from-memory is a skill published in the GitHub repository Chachamaru127/codex-harness (2 stars, last pushed 6mo ago), licensed MIT. It adds 70 tokens to every session and 843 once invoked, about $0.0003 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
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…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
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.
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…