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 Aiyo28/memento-os --skill decidegit clone --depth 1 https://github.com/Aiyo28/memento-osWrote 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/aiyo28/memento-os/decide)<a href="https://agentmods.dev/skills/aiyo28/memento-os/decide"><img src="https://agentmods.dev/badge/skills/aiyo28/memento-os/decide.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.00092 | $0.01152 |
| Opus 5 | $0.00046 | $0.00576 |
| Sonnet 5 | $0.00018 | $0.00230 |
| Haiku 4.5 | $0.00009 | $0.00115 |
Grade A, and why
decide 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 7d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/decide
One skill. Three modes. Every decision produces a reasoning artifact with a priority level.
Setup
The vault path is configured during memento init. If not set, ask the user where their vault lives.
Mode Detection
| Signal | Mode | What happens |
|---|---|---|
| Decision needed from current context | default |
Jump to OODA loop |
| URL, file, or "research this" provided | --research |
Ingest source → extract → then OODA loop |
| "reframe", "different angle", "what am I missing" | --reframe |
Force perspective shift → then OODA loop |
Mode: --research (Ingest First)
Extract knowledge from the source before deciding.
Extraction Engine (5 Fields)
- Core argument — what it argues, not what it's about (1-2 sentences)
- Why it holds — evidence, reasoning, mechanism (3 bullets max)
- Technical specifics — numbers, code patterns, tools. "None" if none
- Execution pattern — the craft move worth stealing. Omit if N/A
- Open questions — what connects to existing work? What assumption might break?
After extraction, ask: "Does this inform a decision, or is it reference material?"
- Decision → continue to OODA loop
- Reference only → save to project Research/ folder, stop
Mode: --reframe
Force a perspective shift before presenting options:
- Invert the question — "What if we did the opposite?"
- Change the timeframe — "What matters in 6 months vs today?"
- Change the stakeholder — "What would the end user prioritize?"
- Expose assumptions — "What are we assuming that might not be true?"
Then enter the OODA loop with the expanded frame.
Retrieval Gate
Before presenting options, search the vault for prior decisions on this topic:
- Scan project
_context.mdActive Reasoning Artifacts table for[D]entries matching the decision domain - Glob
{vault_path}/Knowledge/*{topic}*for existing knowledge notes - Glob
{vault_path}/Projects/*/Decisions/*{topic}*for cross-project decisions - If prior decision found:
- Surface it: "Existing decision: [D] {statement} — {date}"
- Ask: "Reaffirm, revise, or override?"
- If no prior decision: proceed with fresh analysis
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.
- 7d ago First seen · 127 lines · 92 tokens per session scan A 5200939ed95e
decide is a skill published in the GitHub repository Aiyo28/memento-os (3 stars, last pushed 2d ago), licensed MIT. It adds 92 tokens to every session and 1,152 once invoked, about $0.0005 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
impeccable
Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states.…
tree-ring-memory
Guides AI agents in using Tree Ring Memory for durable recall, project decisions, user preferences, warnings, future seeds, privacy-safe memory capture, and lifecycle-aware forgetting.
memory-to-skill
Turn workflows from your MemSearch memory into reusable skills. Use when the user asks to make/create/extract/distill a skill from what they just did or from past work, review skill candidates, install a distilled skill, or 'turn this into a skill'. Manages MemSearch procedural-memory candidates under…
init
Install or update OwnMem in the current repository. Use when the user asks to set up OwnMem, add local project memory for coding agents, or refresh an existing OwnMem installation after a version bump.
mnemo-cortex
Installs and wires Mnemo Cortex (local-first persistent memory) into OpenClaw and other MCP-capable agents. Use for cross-session recall, decision history, or multi-agent shared memory.
honcho-integration
Integrate Honcho memory into existing Python or TypeScript codebases. Use when adding Honcho SDK, setting up peers, configuring sessions, and accessing Honcho's representation.