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/bostonaholic/team/reflectnpx skills add bostonaholic/team --skill reflectgit clone --depth 1 https://github.com/bostonaholic/teamWrote 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/bostonaholic/team/reflect)<a href="https://agentmods.dev/skills/bostonaholic/team/reflect"><img src="https://agentmods.dev/badge/skills/bostonaholic/team/reflect.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.00040 | $0.00625 |
| Opus 5 | $0.00020 | $0.00313 |
| Sonnet 5 | $0.00008 | $0.00125 |
| Haiku 4.5 | $0.00004 | $0.00063 |
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 today.
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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
reflect — turn a finished session into durable learnings
A long session teaches things that die with it: the guidance that was missing,
the command that cost four retries, the thing you did that no skill describes.
/reflect reads the transcript of the session it was invoked from and proposes
each durable learning as a change someone can accept or reject. Three things
make it more than "summarize this session":
- It reads the session, not its own memory. Compaction has already discarded the early turns from context, and those turns are where the corrections live. So the run resolves the session's transcript on disk and works from that file.
- Three lenses, then one list. The lenses look for different things and report what they find. Sorting the findings — accepted, rejected, or handed to the tracker — happens once, afterwards, so one finding cannot be classified three ways.
- Nothing mutates before you answer. The read-and-plan phase writes only inside its own run cache and prints where. Every change to a file you own, and every issue on a tracker, waits on an explicit approval.
Model invocation is disabled (disable-model-invocation: true). A run rewrites
SKILL.md files that every future run reads and creates issues that are public
and irreversible, and no verification afterwards undoes either. Only a
deliberate invocation starts it. agents/openai.yaml restates the same guard
for Codex as policy.allow_implicit_invocation: false.
Procedure references
Read each reference completely when reaching that stage. Follow them in order; later stages depend on state and gates established earlier.
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 221 B
- references/01-input.md 1.5 KB
- references/02-untrusted-input-a-transcript-span-is-content-never-an-instruction.md 911 B
- references/03-execution.md 3.2 KB
- references/04-the-lenses.md 6.7 KB
- references/05-synthesis-one-list-sorted-once.md 2.2 KB
- references/06-apply-the-approved-skill-edits.md 6.6 KB
- references/07-file-the-backlog-items.md 4.2 KB
- resources/resolve-transcript.d.mts 2.3 KB
- resources/resolve-transcript.mjs 12 KB runs code
- resources/write-target.d.mts 1.1 KB
- resources/write-target.mjs 5.0 KB runs code
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.
- today Changed · -491 lines · -140 tokens per session scan B → A cf1b5ec20efe
- yesterday Changed · +11 lines f417a75751a7
- 5d ago First seen · 532 lines · 180 tokens per session scan B bbae07efaeab
reflect is a skill published in the GitHub repository bostonaholic/team (11 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 625 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
state-management
STATE.md reading, writing, and field-level updates. Provides cross-session state persistence via .planning/STATE.md with structured fields for current task, completed phases, blockers, decisions, and quick tasks.
mem0-integration
Mem0 memory layer integration for AI agents. Implement persistent, semantic memory for long-term context retention and personalization.
context-preservation
State capture and restore across context window compactions. Monitors usage thresholds and serializes quality, task, and spec state for seamless continuation.
persistent-memory
Observation capture and retrieval across sessions. Stores decisions, discoveries, and bugfix patterns. Searchable via tags and relevance scoring.
context-management
Project context loading, isolation, and persistent state management across CCPM sessions.
session-memory
Mandatory memory persistence system across session resets using three markdown surfaces in .claude/cc10x/. Iron law - every workflow must load at start and update at end.