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 topprismdata/cultivating-ml-agent --skill runtime-reflexiongit clone --depth 1 https://github.com/topprismdata/cultivating-ml-agentWrote 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/topprismdata/cultivating-ml-agent/runtime-reflexion)<a href="https://agentmods.dev/skills/topprismdata/cultivating-ml-agent/runtime-reflexion"><img src="https://agentmods.dev/badge/skills/topprismdata/cultivating-ml-agent/runtime-reflexion.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.00066 | $0.00930 |
| Opus 5 | $0.00033 | $0.00465 |
| Sonnet 5 | $0.00013 | $0.00186 |
| Haiku 4.5 | $0.00007 | $0.00093 |
Grade A, and why
runtime-reflexion 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Runtime Reflexion (Error → Diagnose → Retry)
Context
Static skills freeze knowledge. Reflexion (Shinn et al. NeurIPS 2023) + Code Sandbox makes ML agents self-correct: 80%+ of runtime errors auto-fixable when errors are precisely classified. agy verified this as a P0 must-have for ML agents (MLE-bench Kaggle medal correlation).
The core insight: errors aren't random — they fall into ~12 categories, each with known fixes.
Guidance
Single Execution with Diagnosis
from framework.src.reflexion import CodeSandbox, ErrorAnalyzer, execute_with_analysis
sandbox = CodeSandbox(timeout_sec=30)
result, diagnosis = execute_with_analysis(generated_code, sandbox)
if not result.success:
print(f"Error: {diagnosis.category.value}")
print(f"Suggested fix: {diagnosis.suggested_fix}")
print(f"Related skills: {diagnosis.related_skills}")
# → "category=memory, fix=reduce batch_size, skills=[gpu-readiness-assessment]"
Self-Correction Loop
from framework.src.reflexion import ReflexionLoop, CodeSandbox
def my_llm_fix(prompt: str) -> str:
"""Call Claude/your LLM to fix code given the reflexion prompt"""
return llm_client.messages.create(
model="claude-sonnet-4-6",
messages=[{"role": "user", "content": prompt}],
).content[0].text
loop = ReflexionLoop(
sandbox=CodeSandbox(timeout_sec=60),
llm_fix=my_llm_fix,
)
result = loop.run(initial_code, max_attempts=5)
if result.success:
deploy(result.final_code)
else:
log_to_vault(result.final_diagnosis) # remember for next time
Error Categories (12)
| Category | Trigger | Fix |
|---|---|---|
syntax |
SyntaxError | Check indentation |
import |
ModuleNotFoundError | pip install |
shape |
shape mismatch | reshape/transpose |
memory |
CUDA OOM | reduce batch_size |
overfitting |
val_loss diverging | dropout/early stop |
data_leakage |
"leakage" mentioned | check temporal features |
timeout |
timed out | reduce data/optimize |
| ... | ... | ... |
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 · 100 lines · 66 tokens per session scan A d14f537a23b8
runtime-reflexion is a skill published in the GitHub repository topprismdata/cultivating-ml-agent (5 stars, last pushed 9d ago), licensed MIT. It adds 66 tokens to every session and 930 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
huggingface-hub
Hugging Face Hub CLI (hf) — search, download, and upload models and datasets, manage repos, query datasets with SQL, deploy inference endpoints, manage Spaces and buckets.
oh-my-posh
Install, configure, or troubleshoot Oh My Posh/ohmyposh: shell init, themes, segments, Nerd Font icons, and prompt setup on PowerShell, zsh, bash, or fish.
agentsight-bugfix
A five-stage workflow for fixing bugs in AgentSight: understand the report, reproduce the problem, find its cause, make a small code change, and verify the result. AgentSight is a system that observes and analyses agent activity.
install-openviking-memory
Install and configure the OpenViking long-term memory plugin for OpenClaw via natural conversation. Once installed, the plugin automatically captures facts from chats and recalls relevant context before each reply (auto-capture + auto-recall, cross-session). Covers prerequisites, install through OpenClaw's plugin…
rag-blueprint
NVIDIA RAG Blueprint — deploy, configure, troubleshoot, and manage. Handles any RAG action: deploy, install, start, enable, disable, toggle, change, configure, troubleshoot, debug, fix, shutdown, stop, or tear down any RAG feature or service (Agentic RAG, VLM, guardrails, query rewriting, models, search, ingestion…
using-dbt-state
Use when a user is enabling, configuring, optimizing, or debugging dbt State (the server-backed reuse mechanism that clones or skips nodes instead of rebuilding them). Use when they conflate dbt State with the state:modified selector or --state deferral. Use when asked about models rebuilding unexpectedly, views with…