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/pandysp/claude-plugins/reflectnpx skills add pandysp/claude-plugins --skill reflectgit clone --depth 1 https://github.com/pandysp/claude-pluginsWrote 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/pandysp/claude-plugins/reflect)<a href="https://agentmods.dev/skills/pandysp/claude-plugins/reflect"><img src="https://agentmods.dev/badge/skills/pandysp/claude-plugins/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 | $0.00114 | $0.00916 |
| Opus 5 | $0.00057 | $0.00458 |
| Sonnet 5 | $0.00023 | $0.00183 |
| Haiku 4.5 | $0.00011 | $0.00092 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reflect: capture lessons before they fade
A session ended. The work shipped, or hit a natural pause. The friction, surprises, and insights are still warm in context, but they decay fast. The next session won't remember what surprised you today.
This skill is the discipline of capturing what's worth keeping before the context evaporates. The output is durable artifacts: instruction changes, memory entries, note updates, or tooling tickets that help future-you avoid repeating the friction or recreating the insight.
What to surface
Five questions to scan. Ask only those that have real signal:
- What surprised me? Moments where reality didn't match the prior. Usually the highest-signal lessons.
- What friction repeated? Pain that happened more than once this session. Single occurrences are noise; repeats are signal.
- What instruction update would have prevented something today? A rule or default missing from the host, project, or repository instructions that govern this work.
- What pattern emerged that's worth naming? A recurring shape, idiom, or approach that worked. Naming makes it reusable.
- What's worth saving as a durable note? Knowledge that will be useful in future sessions but doesn't fit anywhere yet.
If a question has no signal, skip it. Reflection isn't a checklist to fill. It's a salvage operation.
Where to write
Classify the insight before choosing a destination. Follow the host and workspace's established hierarchy instead of inventing a new store:
- Behavioral instruction: update the applicable host, project, or repository instruction file. Common host-level names include
CLAUDE.mdandAGENTS.md, but the governing workspace instructions decide the real destination and scope. - Durable fact: use the host's memory mechanism when one exists and the fact belongs there.
- Project or domain knowledge: update the existing project notes or documentation closest to the subject.
- Session context: use daily or session memory only when the workspace defines it and the information is short-lived.
- Tooling friction: create or update the relevant ticket when the remedy is a code or process change, not another instruction.
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.
- 3d ago First seen · 55 lines · 114 tokens per session scan A 25cb33a296a5
reflect is a skill published in the GitHub repository pandysp/claude-plugins (5 stars, last pushed 12d ago), licensed MIT. It adds 114 tokens to every session and 916 once invoked, about $0.0006 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.
Other skills, from other repositories
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
auditing-subgroup-fairness
Audit an OpenMed NER or de-identification model for performance disparities across demographic subgroups (sex, age band, race/ethnicity when available) using openmed.eval.fairnessreport. Use when the user wants per-subgroup recall and leakage, wants to check whether de-identification under-protects a group, wants to…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…