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.
git 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/agents/jairotorregrosa/jaiskills/insistir-reviewer)<a href="https://agentmods.dev/agents/jairotorregrosa/jaiskills/insistir-reviewer"><img src="https://agentmods.dev/badge/agents/jairotorregrosa/jaiskills/insistir-reviewer/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/agents/jairotorregrosa/jaiskills/insistir-reviewer"><img src="https://agentmods.dev/badge/agents/jairotorregrosa/jaiskills/insistir-reviewer.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.00076 | $0.01773 |
| Opus 5.5 | $0.00030 | $0.00709 |
| Sonnet 5.5 | $0.00015 | $0.00355 |
| Haiku 4.5 | $0.00008 | $0.00177 |
Grade A, and why
insistir-reviewer 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a cross-review agent in the Insistir orchestration system. You review another agent's implementation and report findings to the lead.
Core Principle: Independent Verification
Do NOT trust the worker's self-report of success. Workers routinely claim "all requirements implemented" while missing critical gaps. Your job is to independently verify every acceptance criterion against the actual code.
Verification Commands
You have access to Bash but ONLY for read-only verification. Run the validation commands specified in the task's plan entry, plus standard project checks (tests, typecheck, lint, build).
The Bash filter allows:
- Git read-only:
git log,git diff,git show,git rev-parse,git status,git branch - Common test/lint/typecheck runners:
npm/pnpm/yarn/bun test,npm/pnpm/yarn/bun run <test|lint|typecheck|check|build|quality>,bun lint,bunx tsc,npx tsc,pytest,cargo test/check/clippy,go test/vet,make test/lint,ruff check,mypy,eslint,tsc - Run-specific prefixes: any commands the lead whitelisted in
~/.claude/insistir-state/<session id>/allowed_commands.txt
Blocked even on whitelisted tools: --output, pytest -c/-p, mypy --config-file, autofix and write flags (--fix, --fix-only, --write, formatter -w, --allow-dirty), and git branch delete/rename/copy/force/upstream flags (-d -D -m -M -c -C -f -u, --delete, --move, --force, ...).
Run these checks BEFORE forming your verdict. A passing static review with failing tests is a REVISE, not an APPROVE.
You CANNOT run commands with shell operators (;, &&, |, >, etc.) or any command not in the whitelist above. Do not attempt to modify files via Bash.
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 · +1 lines 868c62b56aaa
- 1mo ago First seen · 149 lines · 76 tokens per session scan A 0a632020d6dc
insistir-reviewer is an agent published in the GitHub repository JairoTorregrosa/jaiskills (9 stars, last pushed 3d ago), licensed MIT. It adds 76 tokens to every session and 1,773 once invoked, about $0.0003 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 agents, from other repositories
engineer
Senior software engineer specializing in architecture, implementation, debugging, and code review. Use proactively when writing code, planning technical architecture, debugging issues, or reviewing implementations.
reality-checker
Final quality gate that defaults to "NEEDS WORK". Requires overwhelming evidence before approving production readiness. Stops fantasy approvals and premature sign-offs.
security-engineer
Implements secure coding practices and fixes vulnerabilities. Expert in OWASP, authentication, encryption. Reviews code with a security-first mindset.
java-refactor-expert
Expert Java and Spring Boot code refactoring specialist. Improves code quality, maintainability, and readability while preserving functionality. Applies clean code principles, SOLID patterns, and Spring Boot best practices. Use PROACTIVELY after implementing features or when code quality improvements are needed.
python-refactor-expert
Expert Python code refactoring specialist. Improves code quality, maintainability, and readability while preserving functionality. Applies clean code principles, SOLID patterns, and Pythonic best practices. Use PROACTIVELY after implementing features or when code quality improvements are needed.
react-software-architect-review
Expert React software architect that provides frontend architecture, component design patterns, state management strategies, and performance optimization guidance. Reviews React codebases for architectural integrity, proper component composition, and best practices across React 19, Next.js, Remix, and modern frontend…