Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/calionauta/stelownpx agentmods add skills/calionauta/stelow/stelow-workflow-execution-critiqueWrote 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/calionauta/stelow/stelow-workflow-execution-critique)<a href="https://agentmods.dev/skills/calionauta/stelow/stelow-workflow-execution-critique"><img src="https://agentmods.dev/badge/skills/calionauta/stelow/stelow-workflow-execution-critique/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/calionauta/stelow/stelow-workflow-execution-critique"><img src="https://agentmods.dev/badge/skills/calionauta/stelow/stelow-workflow-execution-critique.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00092 | $0.03644 |
| Opus 5 | $0.00046 | $0.01822 |
| Sonnet 5 | $0.00018 | $0.00729 |
| Haiku 4.5 | $0.00009 | $0.00364 |
Grade A, and why
stelow-workflow-execution-critique 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 — 424 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execution Critique
sem diffis the primary diff tool. Whensemis available, always usesem difffirst for entity-level change detection (functions, types, methods). Usegit diffonly as fallback whensemis absent. The entire skill follows this convention — the fallback table in Tool Availability covers everysemcommand's git equivalent.
Standalone awareness: when inside stelow, reads scope + mode from .stelow/*/plans/spec-tech*.md and stelow.json. When standalone, auto-detects input type (plan path, directory, URL, or nothing). The HAS_WORKFLOW_DIR flag gates stelow-specific features; all audit criteria work in both modes.
Overview
Run a structured audit after any implementation — whether it followed the full
stelow or was done ad-hoc. Every evaluation criterion runs in
every mode; only the source of truth differs based on what input is available.
Tools: See
../stelow-workflow-orchestrator/references/cli-tools/subagents.mdfor subagent patterns. For large outputs, usebashwith output truncation, orreadwith offset/limit.
🔀 Input Detection
Detect the input type before proceeding:
Input received:
├── Is a path ending in spec-tech*.md?
│ └→ 🗺️ Mode: Workflow Audit (source of truth = plan scopes)
├── Is a path ending in spec-product*.md or spec-*.md?
│ └→ 📋 Mode: Plan Audit (source of truth = product spec)
├── Is a directory path or URL?
│ └→ 📁 Mode: Context Audit (source of truth = sem diff + git + session)
├── User described what changed verbally?
│ └→ Use description to scope the audit. Still run sem diff / git diff
│ to auto-discover changes, but use inline text as the primary
│ scope anchor for what to evaluate.
└── NOTHING / no input?
└→ 💻 Mode: Standalone Audit (source of truth = auto-discovered)
Run: sem diff HEAD~1 (or git fallback), git diff, session file list
If nothing found: ask "What changed?"
What ships with it
3 files 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.
- yesterday Changed · -364 lines 4e920fd9865b
- 10d ago First seen · 788 lines · 92 tokens per session scan A 0f3483e12026
stelow-workflow-execution-critique is a skill published in the GitHub repository calionauta/stelow (10 stars, last pushed yesterday), licensed MIT. It adds 92 tokens to every session and 3,644 once invoked, about $0.0005 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-30.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…