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 commands/whitequeen306/code-cortex-loop/cortexloop-reflectgit clone --depth 1 https://github.com/whitequeen306/code-cortex-loopWhat 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.00015 | $0.00429 |
| Opus 5 | $0.00008 | $0.00215 |
| Sonnet 5 | $0.00003 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
cortexloop-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 yesterday.
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.
What it actually says
/cortexloop-reflect
Manually trigger reflect-and-learn — the automatic step that runs after Direct mode.
When to use
- You applied fixes outside
/cortexloopbut want to capture reusable patterns - A Direct run completed but reflect was skipped
- You want to curate playbook entries after reviewing a successful fix session
Prerequisites
- Recent fixes with passing tests (or you clearly document what was fixed)
- Ideally
docs/cortexloop/report.jsonexists (before/after scores help)
Flow
1. Load context
Read:
skills/reflect/SKILL.md(installed reflect skill)rules/learning-loop.mdccortexloop.config.json→learningblock (if present)docs/cortexloop/report.jsonand relevant git diff
2. Produce outputs
- Append section to
docs/cortexloop/08-reflection.md(incremental log — use 运行时间 from run-meta, not ISO) .cortexloop/reflection.json— structured entries (max 3–5 generalizable patterns)
Follow curation rules in the reflect skill: methods not diffs, patterns not one-offs.
3. Record to playbook
From project root:
node scripts/playbook.mjs record .cortexloop/reflection.json
Add --global if learning.global is enabled in config.
4. Confirm
Report:
- How many entries added vs updated
- Playbook path(s) written
- Reminder: playbook hits are suggestions — next run still verifies via refactor-safety + tests
Notes
- This command does not re-run analysis or apply fixes
- For a full pipeline with auto-reflect, use
/cortexloopin Direct mode instead
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.
- yesterday First seen · 61 lines · 15 tokens per session scan A 68e04a2fbe2e
cortexloop-reflect is a command published in the GitHub repository whitequeen306/code-cortex-loop (15 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 429 once invoked, about $0.0001 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 commands, from other repositories
learn
Force claude-smart to extract learnings from this session now.
component
Scaffold a new React component grounded in the paper-mono primitives. Requires explicit kind or a nearest-existing-component match. No empty divs, no speculative scaffolding.
memory-store
Store an insight, decision, or pattern to memory.
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
no-vibe
Enter no-vibe mode in OpenCode (tutor mode, no direct project file writes).
teach-me-testing
Teach testing progressively through structured sessions. Use when user says ""lets learn testing"" or ""I want to study test practices"".