reflect

A command for recording what happened after an outcome and linking it to stored memories in the Gnosys database. It can mark the outcome as a success or failure.

In plain words
What is it for?
Use it after events such as a deployment or failed refactor to add notes, connect related memory IDs, and adjust confidence.
Why use it?
It keeps the system's confidence in past information aligned with real results instead of leaving memories unchanged.

Command

Install

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.

agentmods
npx agentmods add commands/proticom/gnosys/reflect
Clone the repo
git clone --depth 1 https://github.com/proticom/gnosys
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 581 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00581
Opus 5 $0.00000 $0.00291
Sonnet 5 $0.00000 $0.00116
Haiku 4.5 $0.00000 $0.00058

Measured yesterday against content hash d97685a7774d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

reflect 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 yesterday.

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.

docs/commands/reflect.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

gnosys reflect

Reflect on an outcome to update memory confidence and create relationships in the central Gnosys database.

Usage

gnosys reflect "deploy succeeded"
gnosys reflect "auth refactor failed" --failure --memory-ids mem-1,mem-2
gnosys reflect "hotfix shipped" --notes "rolled back within 10 minutes" --confidence-delta 0.15 --json

Arguments

Argument Description
outcome Short description of what happened

Options

Option Description
--memory-ids <ids> Comma-separated memory IDs to relate to the outcome
--failure Mark the outcome as failure (default: success)
--notes <text> Additional reflection notes
--confidence-delta <n> Custom confidence delta (e.g. 0.1 or -0.2)
--json Output reflection result as JSON

Prerequisites

Requires the central Gnosys database with better-sqlite3 available.

Request mapping

The handler builds sandbox params:

  • outcome — from positional argument
  • success!opts.failure
  • memory_ids — split/trim from --memory-ids when set
  • notes — from --notes when set
  • confidence_delta — parsed float from --confidence-delta when set

Sent via handleRequest with id: "cli-reflect" and method: "reflect".

Human output

Reflection recorded:
  ID:                    refl-abc123
  Outcome:               deploy succeeded
  Memories updated:      2
  Relationships created: 3
  Confidence delta:      +0.10

JSON output

Success emits the sandbox result object via JSON.stringify(result, null, 2).

On failure with --json:

{
  "ok": false,
  "error": "error message"
}

Errors

  • Missing DB driver: install message then exit 1.
  • Sandbox error: Reflect failed: ... then exit 1.
  • Unexpected exception: JSON or human error, then exit 1.

DB is closed in finally even when errors occur.

Validation

cd gnosys-public
npm run cli -- reflect --help
npx vitest run src/test/reflect-command-handler.test.ts

Read the full file on GitHub · 89 lines

Changes

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.

  1. yesterday First seen · 89 lines · 0 tokens per session scan A d97685a7774d

Subscribe to this mod's changes

reflect is a command published in the GitHub repository proticom/gnosys (4 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 581 tokens. 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.