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 skills/wesleysimplicio/simplicio-loop/simplicio-reviewnpx skills add wesleysimplicio/simplicio-loop --skill simplicio-reviewgit clone --depth 1 https://github.com/wesleysimplicio/simplicio-loopWhat 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.00144 | $0.01503 |
| Opus 5 | $0.00072 | $0.00751 |
| Sonnet 5 | $0.00029 | $0.00301 |
| Haiku 4.5 | $0.00014 | $0.00150 |
Grade A, and why
simplicio-review 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 2d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
simplicio-review — thermo-nuclear adversarial review
A single reviewer rubber-stamps; independent reviewers refute. This skill runs the
simplicio-tasks Step 4c adversarial-verify gate as a standalone, reusable review: it fans out
parallel subagents on DISTINCT rubrics, each prompted to REFUTE, then synthesizes a single
deduped verdict.
Credit: distilled from cursor thermos (parallel background subagents, separate
security vs code-quality rubrics, dedup-on-synthesis) wired into the simplicio evidence spine.
When to use
- Before merging ANY item, TRIVIAL through CRITICAL (the Step 4c gate) —
simplicio-tasks' 6-agent floor (Step 3) has no solo/self-review path left; this fan-out is 3 of those 6 roles, always. - "review this branch hard", "thermo-nuclear", "find what's wrong before I merge".
Step 1 — Gather context ONCE (parent)
Collect, in the parent, so subagents don't each re-derive it:
git diff <base>...HEAD # the change set (clamp via simplicio-orient: stat + hunks)
git diff --name-only <base>...HEAD
# full contents of each changed file (signatures-only for unchanged neighbors)
# the item body + acceptance criteria (simplicio-tasks Step 2b-1)
# the run-verification evidence (Step 4b) + any existing PR review threads / bot comments
Scope is added/modified lines only. Pre-existing issues outside the diff are out of scope unless the change makes them reachable.
Step 2 — Fan out parallel reviewers (one message, background)
Spawn 3 INDEPENDENT subagents IN A SINGLE MESSAGE (so they run concurrently — wall-clock down, no proportional token blow-up). Each gets the SAME context bundle and a DISTINCT rubric:
Rubric A — security & correctness
- Real bugs in changed lines: logic errors, off-by-one, null/None, race, resource leak.
- Breaking changes: changed signatures/behavior that break existing callers (grep the callers).
- Security: injection, secret in diff, authz gap, unsafe deserialization, SSRF, path traversal.
- Acceptance criteria: find any AC NOT met. Find any fake/placeholder return
(
Ok(fake)/return None/stubbed success where behavior was required). - Feature-flag / debug leaks: left-on flags, commented-out guards,
console.log/dbg!.
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.
- 2d ago First seen · 105 lines · 144 tokens per session scan A 55181a9a6660
simplicio-review is a skill published in the GitHub repository wesleysimplicio/simplicio-loop (2 stars, last pushed 3d ago), licensed MIT. It adds 144 tokens to every session and 1,503 once invoked, about $0.0007 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
orbit-upgrade
Upgrade the installed orbit plugin to the latest version from GitHub and show what changed. Use when the user says "upgrade orbit", "update agentic loop", "get the latest orbit", or when the /orbit preamble reports UPGRADEAVAILABLE. Speech-to-text aliases: "update agent loop", "upgrade the agent loop".
gemini-vision
Analyze images using Google Gemini 2.0 Flash with proxy support, retry logic, and mock mode.
orbit
Transform any product repository into a production-grade, self-prompting agentic loop system following Daisy Hollman's "build a system that prompts itself" methodology. Audits the current project, then scaffolds persistent memory (CLAUDE.md + STATE files), a specialized sub-agent team, domain skills, a…
develop-web-game
Use when Codex is building or iterating on a web game (HTML/JS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots/text, and review console errors with rendergametotext.
stock-explorer
A Yahoo Finance (yfinance) powered financial analysis tool. Get real-time quotes, generate technical indicator reports (RSI/MACD/Bollinger/VWAP/ATR), summarize fundamentals, and run a one-shot report that outputs a text summary.
agent-integration
Run all three agent integration phases sequentially: research, write-tests, and implement using E2E-first TDD (unit tests written last). For individual phases, use /agent-integration:research, /agent-integration:write-tests, or /agent-integration:implement. Use when the user says "integrate agent", "add agent…