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 JairoTorregrosa/jaiskills --skill insistirgit clone --depth 1 https://github.com/JairoTorregrosa/jaiskillsWrote 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/jairotorregrosa/jaiskills/insistir)<a href="https://agentmods.dev/skills/jairotorregrosa/jaiskills/insistir"><img src="https://agentmods.dev/badge/skills/jairotorregrosa/jaiskills/insistir/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/jairotorregrosa/jaiskills/insistir"><img src="https://agentmods.dev/badge/skills/jairotorregrosa/jaiskills/insistir.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.00034 | $0.04181 |
| Opus 5.5 | $0.00014 | $0.01672 |
| Sonnet 5.5 | $0.00007 | $0.00836 |
| Haiku 4.5 | $0.00003 | $0.00418 |
Grade B, and why
insistir scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
find ~/.claude/insistir-state/${CLAUDE_SESSION_ID} -maxdepth 1 -name '*.approved' -delete How it starts
The opening of the file, as written. The whole thing — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
insistir
Task: $ARGUMENTS
You are the tech lead of the pipeline below. Empty task line → get the task in Phase 0.
It pays off for multi-part work that parallelizes across different files. For single-file edits, typos, quick fixes, strictly sequential chains, or tasks that must all edit the same file (parallel workers overwrite each other), tell the user a single session is cheaper and confirm before going on.
Pipeline
LEAD (delegate mode: plans, spawns, routes reports, writes markers; never edits code)
│
├─► worker-t1 worker-t2 worker-t3 implement + commit → done
│ │ │ │
├─► reviewer-t1-r1 reviewer-t2-r1 reviewer-t3-r1 fresh, read-only, never the author
│ │ │ │ → verdict JSON → done
├─► second-opinion judge (cross-provider; skipped on trivial clean approvals)
│ │
│ APPROVED ─► T<N>.approved marker ─► TaskUpdate completed (hook-gated)
│ REVISE ─► fixer-t<N>-r1 (fresh) ─► reviewer-t<N>-r2 (fresh) ─► judge ─► …
│ until APPROVED, or max_review_rounds → FAILED (suggest decomposition)
└─► next wave once dependencies are completed
Invariants
- Delegate mode from Phase 2 on. The lead spawns, routes reports, manages tasks and reports
to the user. It never reads or edits code, runs builds or tests. Lead Bash is limited to: the
mode check, the pre-flight check, the state dir, approval markers, the judge diff, what the
second-opinionandfile-todosskills run, andinsistir.py. - Fresh agent per phase. Every worker, reviewer and fixer is spawned for one job and ends after its report. Nothing is reused or resumed across rounds.
- Reviewer is never the author and cannot edit (
disallowedToolsplus a Bash whitelist hook). Its evidence is the code and the checks it runs, not the worker's report. - Acceptance criteria are the contract. Paste them verbatim into every prompt.
- A plan task completes only after an APPROVED outcome, recorded as a marker the TaskCompleted hook checks. Never write a marker to unblock the gate.
- Round budget:
max_review_rounds(default 2, per-task override). Exhausted = failed. - The judge never blocks the run. Unavailable judge → reviewer verdict stands, recorded.
What ships with it
10 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.
- agents/openai.yaml 180 B
- hooks/reviewer_bash_filter.py 7.7 KB runs code
- hooks/task_completed.py 5.0 KB runs code
- references/crew-fallback.md 4.5 KB
- references/deepen-plan.md 2.9 KB
- references/edge-cases.md 4.5 KB
- references/plan-template.md 2.6 KB
- references/spawn-prompts.md 3.7 KB
- references/summary-template.md 1.6 KB
- scripts/insistir.py 7.6 KB runs code
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 Changed · -258 lines · -178 tokens per session scan D → B 244cde56587c
- 1mo ago First seen · 507 lines · 212 tokens per session scan D e649b6d07315
insistir is a skill published in the GitHub repository JairoTorregrosa/jaiskills (10 stars, last pushed 4d ago), licensed MIT. It adds 34 tokens to every session and 4,181 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
review
Review code, specifications, or designs for quality, bugs, security, and best practices. Use when the user wants feedback on recent work, a pull request, or any artifact.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
sip
After you create or change an artifact or skill, taste-test it with our own skills instead of trusting your in-session judgment — recursive self-improvement, made automatic. Use right after writing or editing anything, before calling it done, committing, or handing it off.
prism
Split one artifact — a claim, plan, or file — across 2 to 5 independent lenses, one per genuinely distinct failure mode (correctness, security, readability, cost, adversarial-user), and return their convergence: where they agree, where they disagree, and the single next question that resolves the disagreement. Use…
hate
Attack a plan, design, or argument like you want it to fail before you commit real effort — return the single load-bearing objection and the cheapest experiment that would prove it matters, not a checklist. User-invoked on purpose: a hate-it reflex always in the agent's reach would bias it toward demolition. Weighs…
fabric-spec
Starts a persistent Pi Fabric spec supervisor that audits the main session against a feature design spec and steers only when a requirement lacks verified evidence. Use for strict, unblocked spec compliance while the main agent keeps full freedom to orchestrate.