Claude-Mind: Skill for Claude Code

.claude/skills/reflect-on-outcome/SKILL.md

reflect-on-outcome is a skill for Claude Code from zkysar1/Claude-Mind. It costs 101 tokens per session (24,426 once invoked), scanned A, original, MIT.

A reflection process for a completed hypothesis or goal outcome. It records what happened, what execution patterns appeared, and what small hypotheses were resolved.

In plain words
What is it for?
Use it after a hypothesis resolves, after an execution finishes, or when processing several small hypotheses together.
Why use it?
It turns completed work into reusable lessons instead of leaving the reasons for success or failure unrecorded.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: reads .claude/ paths.

This is zkysar1/Claude-Mind's own configuration. It tells Claude Code how to work on Claude-Mind itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Claude-Mind configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is Bash: MIND_AGENT={c} bash core/scripts/experience-read.sh --id {experience_ref}.

Reuse

Borrowing it

Nothing to install: this file belongs to zkysar1/Claude-Mind. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/zkysar1/Claude-Mind/main/.claude/skills/reflect-on-outcome/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/zkysar1/Claude-Mind

Made for: Claude Code.

Wrote 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.

agentmods badge for reflect-on-outcome

README.md
[![agentmods](https://agentmods.dev/badge/skills/zkysar1/claude-mind/reflect-on-outcome/github.svg)](https://agentmods.dev/skills/zkysar1/claude-mind/reflect-on-outcome)
Your own site
<a href="https://agentmods.dev/skills/zkysar1/claude-mind/reflect-on-outcome"><img src="https://agentmods.dev/badge/skills/zkysar1/claude-mind/reflect-on-outcome/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for reflect-on-outcome

Your own site · 80×15
<a href="https://agentmods.dev/skills/zkysar1/claude-mind/reflect-on-outcome"><img src="https://agentmods.dev/badge/skills/zkysar1/claude-mind/reflect-on-outcome.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 101 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 24,426 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Rogue Agent · line 939
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
How audits are shown
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.1 $0.00101 $0.24426
Opus 5 $0.00051 $0.12213
Sonnet 5 $0.00020 $0.04885
Haiku 4.5 $0.00010 $0.02443

Measured 3d ago against content hash e64af4f9ce1b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

reflect-on-outcome 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 3d 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.

.claude/skills/reflect-on-outcome/SKILL.md · 1,945 lines

How it starts

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

/reflect-on-outcome — Outcome-Based Reflection

This sub-skill implements all outcome-based reflection modes for /reflect. It is invoked by the parent router for three modes:

  • Hypothesis mode (--on-hypothesis <id>): Full single-hypothesis reflection pipeline
  • Execution mode (--on-execution): Lightweight execution outcome reflection
  • Batch micro mode (--batch-micro): Batch micro-hypothesis processing

Each mode section below is self-contained with its own step numbering.

Mode: Hypothesis Reflection (--on-hypothesis )

This sub-skill implements Mode 1 of /reflect. It is invoked by the parent /reflect router when --on-hypothesis <hypothesis-id> is specified, or during --full-cycle for each newly resolved hypothesis. It runs the full reflection pipeline: horizon gate, ABC chain analysis, differentiated and contrastive extraction, encoding score, textual reflection, violation tracking, source tracking, journal entry, accuracy reflection, pattern signatures, entity extraction, belief registry, contradiction detection, process-outcome classification, context gap analysis, strategy tracking, experiential index updates, spark check, knowledge reconciliation, and tree growth trigger.

Step 0: Load Conventions

Step 0: Load ConventionsBash: load-conventions.sh with each name from the conventions: front matter. Read only the paths returned (files not yet in context). If output is empty, all conventions already loaded — proceed to next step.

Step 0.5: Horizon Gate

Read the resolved record and check its horizon field (default: "short" if missing).

IF horizon == "micro":
    ERROR: Micro-hypotheses should never reach --on-hypothesis.
    They are batch-reflected via --batch-micro. Abort.

IF horizon == "session":
    Run LIGHTWEIGHT reflection path:
      - Generate ABC chain (Step 2) — abbreviated: skip skill_chain and research_depth
      - Skip Step 2.5 differentiated extraction UNLESS surprise >= 7 — EXCEPT when
        outcome == CORRECTED, where Step 2.5 runs regardless of surprise (its CORRECTED
        branch only; the CONFIRMED branch stays skipped). See "Why CORRECTED is exempt"
        below — do NOT read this as a general fall-through (guard-137).
      - Skip Step 2.6 contrastive extraction
      - Generate encoding score (Step 2.7) — normal
      - Generate textual reflection (Step 3) — abbreviated (3-5 sentences max)
      - Skip Step 3.5 domain-specific reflection
      - Track violation (Step 4) — if corrected, normal
      - Update source tracking (Step 5) — only if external sources used
      - Append to journal (Step 6) — abbreviated entry
      - Accuracy reflection (Step 7) — normal
      - Skip Steps 7.5, 7.5b, 7.6, 7.6b (pattern sigs, entities, beliefs, contradictions)
      - Skip Step 7.6c process-outcome dual score
      - Skip Step 7.7 context gap analysis
      - Run spark check (Step 8) — normal (short hypotheses can still spark insights)
    RETURN after lightweight path — do not continue to full Step 1.

    # Meta-strategy category depth override
    Bash: meta-read.sh reflection-strategy.yaml
    IF hypothesis.category in category_depth_overrides:
        override = category_depth_overrides[hypothesis.category]
        IF override == "full" AND horizon == "session":
            Log: "META OVERRIDE: session horizon → full pipeline for category {hypothesis.category}"
            CONTINUE to full reflection pipeline (skip lightweight return)

IF horizon == "short" OR horizon == "long" OR horizon is missing:
    Continue to full reflection below.

Read the full file on GitHub · 1,945 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. 3d ago Changed e64af4f9ce1b
  2. 7d ago Changed · +14 lines 10564ca029f8
  3. 11d ago First seen · 1,931 lines · 101 tokens per session scan A a6ead9390f03

Subscribe to this mod's changes

reflect-on-outcome is a skill published in the GitHub repository zkysar1/Claude-Mind (5 stars, last pushed 3d ago), licensed MIT. It adds 101 tokens to every session and 24,426 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.

Related

Other skills, from other repositories

hive.browser-automation

Required before any hive-browser CLI command. The browser is driven from the terminal by running hive-browser ... --json via terminalexec — not via MCP tools. Teaches the browser lifecycle rules (the bridge attaches to the USER'S running Chrome — never kill or launch browser processes; timeouts are transport issues…

aden-hive/hive · 142 tokens

hive.worker-delegation

Concrete patterns for breaking colony work into parallel worker jobs via runplaybook — when fan-out helps, how to model the goal as a tracker table, write the worker skill, author the playbook, pilot, and let convergence retry/resume the gap.

aden-hive/hive · 58 tokens

hive.linkedin-automation

Read before automating LinkedIn with browser tools. LinkedIn combines shadow DOM (#interop-outlet), strict Trusted Types CSP that silently drops innerHTML, Lexical composer, native beforeunload dialogs that hang the bridge, and aggressive spam filters — each has bitten us at least once. Verified flows for profile…

aden-hive/hive · 99 tokens

hive.x-automation

Read before automating X / Twitter with browser tools. Verified flows for post, reply, delete, search-and-engage, plus the Draft.js compose quirks that silently disable the send button. Includes the daily-reply and job-market-reply playbooks. Requires hive.browser-automation for the underlying screenshot + coordinate…

aden-hive/hive · 81 tokens

hive.slack-notifications-setup

Set up a Slack notification channel (Sentinel) for a colony by driving the browser — reuse or create the "Hive Sentinel" Slack app from a JSON manifest, install it, capture the bot + app tokens, create/select the channel via the Slack API, and turn Sentinel on so the colony can ping the user on Slack and accept…

aden-hive/hive · 136 tokens

hive.writing-hive-skills

Author a new Agent Skill for a Hive agent that conforms to the Agent Skills specification (SKILL.md with YAML frontmatter, optional scripts/references/assets directories). Use when the user asks to create, scaffold, add, or package a new skill for a Hive agent.

aden-hive/hive · 63 tokens