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/stilero/claude-plugins/reflectgit clone --depth 1 https://github.com/stilero/claude-pluginsWhat 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.00022 | $0.00530 |
| Opus 5 | $0.00011 | $0.00265 |
| Sonnet 5 | $0.00004 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are invoking the meta-reflector manually. The agent-harness plugin's
self-improvement loop is normally count-triggered (every 5 completed runs from
the orchestrator's Stage 5), but this command lets you force a meta-run
on-demand or scheduled externally via scripts/run-meta.sh.
Process
-
Inspect the slash-command argument string. If
$ARGUMENTScontains the token--dry-run:-
Dispatch the
meta-reflectorsubagent (via the Task tool) with this instruction prepended to its normal context:DRY RUN: produce the reflection file and show the intended change as a diff, but do NOT edit any agent or config file, do NOT commit anything to the plugin repo, and do NOT open any PR. Print the proposed diff in the reflection's
## Change appliedsection as a fenceddiffblock. Skip Step F (stats.md rewrite) soruns_since_last_metastays at its current value. -
Otherwise (no
--dry-run): dispatch themeta-reflectorsubagent with no extra prefix. It will follow its own algorithm (Steps A–G inagents/meta-reflector.md).
-
-
When the subagent returns, parse its JSON output (
{ "reflection_path": "...", "change_applied": true|false, "verdict_prior": "..." }). -
Report to the user, in two short paragraphs:
- The reflection file path.
- What changed if anything (commit SHA + summary), or "no change applied" with the reason.
- The verdict on the prior change (SUSTAIN, FLAG, AUTO-REVERT, AUTO-REVERT-FAILED, or no-prior-change).
- Any workflow-proposal PRs opened, with URLs.
Hard rules
- You do NOT execute the meta algorithm yourself. You only dispatch the subagent and relay its output. The subagent is the one with the safety constraints (one-change-per-run, AUTO-REVERT gate, oscillation check, lint-before-commit, max_model ceiling, draft-only PRs).
- Do NOT edit any file from this command. The subagent writes its own reflection and applies its own change.
- If the subagent returns malformed output (no JSON block, missing fields), report the failure verbatim and do not attempt recovery — the next meta-run will see the unchanged state and try again.
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 · 32 lines · 0 tokens per session scan A d5f1fca917c6
reflect is a command published in the GitHub repository stilero/claude-plugins (2 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 530 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.