Borrowing it
Nothing to install: this file belongs to poteto/noodle. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/poteto/noodle/main/.agents/skills/reflect/SKILL.mdgit clone --depth 1 https://github.com/poteto/noodleWrote 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/poteto/noodle/reflect)<a href="https://agentmods.dev/skills/poteto/noodle/reflect"><img src="https://agentmods.dev/badge/skills/poteto/noodle/reflect/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.
<a href="https://agentmods.dev/skills/poteto/noodle/reflect"><img src="https://agentmods.dev/badge/skills/poteto/noodle/reflect.svg" alt="Reviewed on agentmods" width="80" 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.00657 |
| Opus 5.5 | $0.00016 | $0.00263 |
| Sonnet 5.5 | $0.00008 | $0.00131 |
| Haiku 4.5 | $0.00004 | $0.00066 |
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 1mo 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reflect
Review the conversation and persist learnings — to brain/, to skill files, or as structural enforcement.
Process
Use Tasks to track progress (TaskCreate per step, TaskUpdate to in_progress/completed).
- Read
brain/index.mdto understand what notes already exist - Scan the conversation for:
- Mistakes made and corrections received
- User preferences and workflow patterns
- Codebase knowledge gained (architecture, gotchas, patterns)
- Tool/library quirks discovered
- Decisions made and their rationale
- Friction in skill execution, orchestration, or delegation
- Repeated manual steps that could be automated or encoded
- Skip anything trivial or already captured in existing brain files
- Route each learning to the right destination (see Routing below)
- Update
brain/index.mdif any brain files were added or removed
Routing
Not everything belongs in the brain. Route each learning to where it will have the most impact.
Structural enforcement check
Before routing a learning to brain/, ask: can this be a lint rule, script, metadata flag, or runtime check? If yes, encode it structurally and skip the brain note. See brain/principles/encode-lessons-in-structure.md.
Brain files (brain/)
Codebase knowledge, delegation principles, gotchas — anything that informs future sessions. This is the default destination. Use the brain skill for writing conventions.
- One topic per file. File name = topic slug.
- Group in directories with index files using
[[wikilinks]]. - No inlined content in index files.
Skill improvements (.agents/skills/<skill>/)
If a learning is about how a specific skill works — its process, prompts, or edge cases — update the skill directly. Use the skill-creator skill for guidelines on effective skill content.
Orchestration workflow improvements
If the session revealed systemic orchestration issues, route to:
- Brain principle (new delegation heuristic) →
brain/delegation/ - Skill mechanics change (monitoring loop, review step) → relevant skill file
- New skill opportunity (recurring workflow that could be encoded) → note in summary for the user
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.
- 1mo ago First seen · 71 lines · 40 tokens per session scan A d414a01130c8
reflect is a skill published in the GitHub repository poteto/noodle (529 stars, last pushed 7mo ago), licensed MIT. It adds 40 tokens to every session and 657 once invoked, about $0.0002 per session on Opus 5.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
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
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…
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…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.