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 CodeInfinity1/Stram --skill agent-self-reflectiongit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/agent-self-reflection)<a href="https://agentmods.dev/skills/codeinfinity1/stram/agent-self-reflection"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/agent-self-reflection/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/codeinfinity1/stram/agent-self-reflection"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/agent-self-reflection.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.00041 | $0.00600 |
| Opus 5.5 | $0.00016 | $0.00240 |
| Sonnet 5.5 | $0.00008 | $0.00120 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
agent-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 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Self Reflection
Purpose
Run a model-led reflection over recent work so the assistant can understand what happened, what worked, what failed, and what should change. This is a Stram-owned adaptation of external reference self-reflection patterns.
When To Use
Use after a smoke failure, user correction, long debugging session, complex implementation, or any task where future behavior should improve from evidence.
Inputs And Evidence
- Recent audit runs and notes.
- Current
cognitive_state. - User corrections and preferences.
- Test results, tool failures, and recovery actions.
- Current commitments and follow-ups.
Tool Map
cognitive_self_reviewcognitive_self_review_statuscognitive_interaction_reviewcognitive_interaction_review_statuscognitive_skill_evolvememory_writememory_summary
Workflow
- Gather exact evidence from recent work before reflecting.
- Ask the model to separate facts, uncertainty, risks, user impact, and recommended changes.
- Record durable lessons only when supported by evidence.
- Use skill evolution when the lesson is reusable workflow knowledge.
- Use persona evolution only when the evidence reflects communication style or stable user preference.
- Report a concise reflection with concrete next changes.
Safety And Boundaries
- Do not overfit one incident into a permanent rule.
- Do not hide failures; reflection should surface evidence and limitations.
- Do not claim improvement unless the behavior was changed or recorded.
Safety And Approval
- Reflection must not rewrite durable memory, skills, persona, or commitments without evidence and the native tool's approval/validation path.
- Do not store sensitive or speculative user facts from a single ambiguous event.
- Do not use reflection to justify ignoring the user's newest instruction or active task.
- Keep user-facing reflection concise unless the user asks for a detailed postmortem.
Native Implementation Boundaries
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 · 79 lines · 41 tokens per session scan A 97a08ebd3736
agent-self-reflection is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 600 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-31.
Other skills, from other repositories
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.
lighting-report-extract
Check reported lighting quantities and results in supplied simulation PDFs without adding repeated calculation surfaces. Use for scoped luminaire inventories and illuminance results; not simulation or compliance.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.
container-debugging
Diagnose reported container build, startup, network, permission and resource failures. Use when an image or Compose service fails; reproduce against the final image/config and avoid data-destroying cleanup as a workaround.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
pr-review
Comprehensive PR review across six dimensions — cost impact, environment drift, ownership gaps, SOC 2 compliance, deprecated API / version hygiene, and rollback feasibility. Each mode inspects the diff and current file state, reports findings with severity, and recommends concrete fixes. Use when preparing a PR for…