reflect

A conversation-learning procedure that records reliable patterns from corrections, praise, and newly found edge cases. It connects temporary observations with longer-term agent and team notes.

In plain words
What is it for?
Capturing feedback, recording successful or failed approaches, documenting edge cases, and updating agent history or team decisions.
Why use it?
It helps coding agents avoid repeating mistakes and preserve useful decisions across sessions. Important lessons can be reviewed and promoted into shared project guidance.

Skill for Claude CodeCodex

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 skills/bradygaster/squad/reflect
Any agent
npx skills add bradygaster/squad --skill reflect
Clone the repo
git clone --depth 1 https://github.com/bradygaster/squad

Made for: Claude Code, Codex.

Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,711 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.00066 $0.01711
Opus 5 $0.00033 $0.00856
Sonnet 5 $0.00013 $0.00342
Haiku 4.5 $0.00007 $0.00171

Measured 2d ago against content hash a844dcf82122, 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 2d 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.

Origin

Copies of this mod

3 near-identical copies found in the catalogue:

  • reflect — 100% identical, 0 lines differ
  • reflect — 100% identical, 0 lines differ
  • reflect — 100% identical, 0 lines differ
.squad/skills/reflect/SKILL.md · 230 lines

How it starts

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

Reflect Skill

Critical learning capture system for Squad. Prevents repeating mistakes and preserves successful patterns across sessions.

Analyze conversations and propose improvements to squad knowledge based on what worked, what didn't, and edge cases discovered. Every correction is a learning opportunity.


Integration with Squad Architecture

Reflect complements existing Squad knowledge systems:

  1. .squad/agents/{agent}/history.md — Permanent learnings from completed work (append-only; each agent updates their own file; Scribe propagates cross-agent updates)
  2. .squad/decisions.md — Team-wide decisions that all agents respect
  3. reflect skill — Captures in-flight learnings from conversations that may graduate to history.md or decisions.md

Workflow:

  • Use reflect during work to capture learnings
  • At session end, review captured learnings
  • Promote HIGH confidence patterns → lead agent for decision.md review
  • Promote agent-specific patterns → {agent}/history.md updates

Triggers

🔴 HIGH Priority (Invoke Immediately)

Trigger Example Why Critical
User correction "no", "wrong", "not like that", "never do" Captures mistakes to prevent repetition
Architectural insight "you removed that without understanding why" Documents design decisions (Chesterton's Fence)
Immediate fixes "debug", "root cause", "fix all" Learns from errors in real-time

🟡 MEDIUM Priority (Invoke After Multiple)

Trigger Example Why Important
User praise "perfect", "exactly", "great" Reinforces successful patterns
Tool preferences "use X instead of Y", "prefer" Builds workflow preferences
Edge cases "what if X happens?", "don't forget", "ensure" Captures scenarios to handle

🟢 LOW Priority (Invoke at Session End)

Trigger Example Why Useful
Repeated patterns Frequent use of specific commands/tools Identifies workflow preferences
Session end After complex work Consolidates all session learnings

Read the full file on GitHub · 230 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. 2d ago First seen · 230 lines · 66 tokens per session scan A a844dcf82122

Subscribe to this mod's changes

reflect is a skill published in the GitHub repository bradygaster/squad (3,150 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 1,711 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-30.