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/ssube/conclave/self-reflectionnpx skills add ssube/conclave --skill self-reflectiongit clone --depth 1 https://github.com/ssube/conclaveWhat 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.00042 | $0.00640 |
| Opus 5 | $0.00021 | $0.00320 |
| Sonnet 5 | $0.00008 | $0.00128 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
self-reflection 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Self-Reflection Skill
A structured self-review process. Walk through what you've built, what you've learned, what you've forgotten, and what needs attention.
This is not a status check. This is deeper work — examining accumulated context, identifying gaps, and producing actionable insights.
When to Reflect
- After completing a significant body of work
- When the project direction feels unclear
- When asked to reflect or review
- During quiet periods when no urgent tasks demand attention
- At least once per week as part of continuous improvement
Usage
Full reflection
python3 {baseDir}/self_reflection.py --full
Performs all phases:
- Gather — Pull notes, tasks, catalog, recent activity
- Review — Examine accumulated knowledge and context
- Identify — Find gaps, missing skills, workflow friction
- Dream — Draw inspiration and brainstorm improvements
- Act — Produce reflection notes and improvement ideas
- Record — Save the reflection to ChromaDB and optionally to disk
Quick reflection (gather + identify only)
python3 {baseDir}/self_reflection.py --quick
Specific phases
python3 {baseDir}/self_reflection.py --phase gather
python3 {baseDir}/self_reflection.py --phase review
python3 {baseDir}/self_reflection.py --phase dream
Save reflection output to file
python3 {baseDir}/self_reflection.py --full --output /path/to/reflections/
What Gets Reviewed
Context Sources
- ChromaDB notes — What has been learned, observed, decided
- Planka tasks — Recently completed work, upcoming priorities, blocked items
- Data catalog — Item inventory, quality distribution
- Available skills — Skill inventory and coverage
Gap Analysis
- Missing skills — What tools would have made recent work easier?
- Workflow friction — Where do processes break down or feel clumsy?
- Knowledge gaps — What don't you know that you should?
- Consistency — Is communication staying true to project goals?
What ships with it
1 file 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.
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.
- 2d ago First seen · 87 lines · 42 tokens per session scan A 1c0c290c540e
self-reflection is a skill published in the GitHub repository ssube/conclave (2 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 640 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-31.
Other skills, from other repositories
mine
Mine a project or conversation into your MemPalace — extract and store memories for later retrieval.
mempalace-recall
Recall protocol for MemPalace — search the palace before answering about past work, people, projects, or prior decisions. Apply when the user asks what was decided, what happened before, who someone is, what was discussed last time, or anything that may already be filed in their memory palace; or when mempalace-recall…
docker-extend
Use when: User wants to extend Docker with custom tools, personalize the Docker environment, or set up user-specific Docker customization. Triggers: 'extend docker', 'docker-extend', 'add tools to docker', 'customize docker', 'add my tools to the container', 'personalize docker setup', 'docker user setup', 'install…
python-testing
Python testing best practices using pytest including fixtures, parametrization, mocking, coverage analysis, async testing, and test organization. Use when writing or improving Python tests.
database-migrations
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Django, TypeORM, golang-migrate). Use when planning or implementing database schema changes.
docker-patterns
Docker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration. Use when setting up containerized development environments or reviewing Docker configurations.