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 skills add klimentij/klimkit --skill klimkit-reflectorgit clone --depth 1 https://github.com/klimentij/klimkitWrote 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/klimentij/klimkit/klimkit-reflector)<a href="https://agentmods.dev/skills/klimentij/klimkit/klimkit-reflector"><img src="https://agentmods.dev/badge/skills/klimentij/klimkit/klimkit-reflector.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.00050 | $0.00341 |
| Opus 5 | $0.00025 | $0.00170 |
| Sonnet 5 | $0.00010 | $0.00068 |
| Haiku 4.5 | $0.00005 | $0.00034 |
Grade A, and why
klimkit-reflector 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 7d 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.
What it actually says
Klimkit Reflector
Use this after verification and before final review. Reflection is synthesis for future work, not a chronological proof note.
Workflow
- Read the current request, work notes, changed-file summary, verification evidence, intended final result, the repo's
AGENTS.md, and relevantdocs/work/LOGs from earlier work folders (descend selectively — never bulk-load the tree). - Write the reflection as the next numbered note in the current
docs/work/phase folder, e.g.004-reflection.md, headed with a UTC timestamp line likeReflected: YYYY-MM-DDTHH:MM:SSZ. - Use these default sections unless a wider reflection needs more:
ObservationsDerived PatternInsightNext Probe
- Keep each section concise and grounded in evidence.
- Add a one-line entry for the note to the phase
LOG.md. - If the reflection surfaces a preference or process rule that should bind every future session, propose adding it to the repo's
AGENTS.mdinstead of leaving it buried in the note. - Reconsider the work after writing the reflection. If it exposes a material gap, fix the work and rerun impacted verification before final review.
Tiny one-command tasks may mark reflection not applicable, but the reason must be explicit.
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.
- 7d ago First seen · 25 lines · 50 tokens per session scan A 4b10cd7ba9b8
klimkit-reflector is a skill published in the GitHub repository klimentij/klimkit (7 stars, last pushed 27d ago), licensed MIT. It adds 50 tokens to every session and 341 once invoked, about $0.0003 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
durable-session-state
Persist plans, scope decisions, evidence, and reviewer/critic verdicts to durable files during long or multi-phase tasks so work survives context compaction, session resumes, and handoffs. Use for swarm-mode tasks, before context grows large, when recording approval gates, and when resuming after compaction or a…
obsidian
Use the official Obsidian CLI (v1.12+) to manage vaults, notes, daily notes, search, tasks, tags, properties, links, templates, sync, publish, and workspaces. Use when the user mentions Obsidian, vaults, notes, or wants to automate note-taking and knowledge base workflows.
contextdb-autopilot
Automatic ContextDB session lifecycle — init, session events, checkpoints, and continuity artifacts. Use when you need AIOS context persistence without prompt injection. NOT for general task execution — only for ContextDB session management. TRIGGER: contextdb、session persist、checkpoint save.
memo
AIOS project memory — read/write/search your own memory using the memo capabilities. You (the model) decide what to remember, what to correct, and what was useful; the harness only executes your decision. Use when you want to recall prior work, persist a durable fact, supersede a wrong one, or mark a recalled memory…
memory-state
State variables the Sentinel must keep across ticks (last order sent, freeze flag, FATAL streak, per-state counters, emergency history, cooldowns). Use this skill on every tick to update memory and decide if a new order is required (edge-triggered).
aios-offload-recall
Use when recalling prior AIOS tool/browser outputs from offloaded refs; inspect Mermaid canvas first, then read only matching node-level evidence.