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/reasoningbank-intelligencenpx skills add eric-cielo/moflo --skill reasoningbank-intelligencegit 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/reasoningbank-intelligence)<a href="https://agentmods.dev/skills/eric-cielo/moflo/reasoningbank-intelligence"><img src="https://agentmods.dev/badge/skills/eric-cielo/moflo/reasoningbank-intelligence.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.00046 | $0.01306 |
| Opus 5 | $0.00023 | $0.00653 |
| Sonnet 5 | $0.00009 | $0.00261 |
| Haiku 4.5 | $0.00005 | $0.00131 |
Grade A, and why
reasoningbank-intelligence 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 6d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ReasoningBank Intelligence
Trajectory-based learning pipeline for moflo-enabled agents. Records what an agent did, judges the outcome, distills successful runs into reusable patterns, and retrieves relevant prior experience on the next task.
Prerequisites
- moflo (the neural subsystem ships inline as part of the moflo package)
- Moflo's memory DB at
.swarm/memory.db(created on first run)
Quick Start
import { createInitializedReasoningBank } from 'moflo/dist/src/cli/neural/reasoning-bank.js';
const rb = await createInitializedReasoningBank({
namespace: 'reasoning-bank',
vectorDimension: 768,
retrievalK: 3,
mmrLambda: 0.7, // 0=pure relevance, 1=pure diversity
distillationThreshold: 0.6, // min verdict score to keep
dedupThreshold: 0.95,
});
The Pipeline
Four stages. You typically call each once per task:
1. Record trajectory → storeTrajectory({ id, input, actions, outcome, reward, ... })
2. Judge → const verdict = await rb.judge(trajectory)
3. Distill → const memory = await rb.distill(trajectory) // if verdict good enough
4. Retrieve (next task) → const hits = await rb.retrieveByContent(query, k)
1. Record
const trajectory = {
id: taskId,
input: userRequest,
actions: ['read_file', 'edit_file', 'run_tests'],
outcome: 'success' as const,
reward: 1.0, // 0..1
metadata: { toolCalls: 3, durationMs: 1800 },
timestamp: new Date(),
};
rb.storeTrajectory(trajectory);
2. Judge
The built-in judge scores on outcome + reward + action-step quality. No external LLM call.
const verdict = await rb.judge(trajectory);
// { score: 0-1, outcome: 'success' | ..., reasoning: string }
Swap in your own judge by extending ReasoningBank if you want LLM-in-the-loop scoring — this was designed as a rule-based baseline so the hot path stays cheap.
3. Distill
Compresses a trajectory into a reusable DistilledMemory (signature, approach, outcome-tagged). Skips if the verdict is below distillationThreshold.
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.
- 6d ago First seen · 149 lines · 46 tokens per session scan A d7300dc6da96
reasoningbank-intelligence is a skill published in the GitHub repository eric-cielo/moflo (18 stars, last pushed 3d ago), licensed MIT. It adds 46 tokens to every session and 1,306 once invoked, about $0.0002 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
unified-memory
Share durable, inspectable context and handoffs between Claude, Codex, Hermes, Cursor, OpenCode, and other agents through the local ECC Memory Vault. Use when an agent must save work state, transfer context, resume another agent's task, or search shared project knowledge.
strategic-compact
Suggests manual context compaction at logical intervals to preserve context through task phases rather than arbitrary auto-compaction. Use when a session is approaching a context limit and a task phase is a natural place to compact.
agents-md-improver
Audit and improve project-rules files (AGENTS.md, CLAUDE.md, .agents/instructions, local overrides) so the agent keeps accurate project context. Use when the user asks to check, audit, review, update, improve, or fix their AGENTS.md or CLAUDE.md, mentions "project rules maintenance" or "agent context optimization", or…
agents-md-revise
Capture learnings from the current session into the project-rules file (AGENTS.md, CLAUDE.md, or local override) so future sessions benefit. Use when the user says "revise the rules", "update AGENTS.md / CLAUDE.md with what we just learned", "save this to project memory", "remember this for next time", or at the end…
token-optimization
Use when the user says 'token optimization', 'save tokens', 'context window', 'reduce tokens', 'token stack', or 'TokenStack', or asks about extending context window capacity. Covers TokenStack, the built-in compression proxy that shrinks Claude Code tool output before it reaches the Anthropic API. Do NOT use for…
compress
Use when the user says 'tokenstack', 'compression', 'token savings', 'proxy status', or asks about context window usage.