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 alejandro-ventures/llm-agnostic-icm-framework --skill recurrence-reviewgit clone --depth 1 https://github.com/alejandro-ventures/llm-agnostic-icm-frameworkWrote 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/alejandro-ventures/llm-agnostic-icm-framework/recurrence-review)<a href="https://agentmods.dev/skills/alejandro-ventures/llm-agnostic-icm-framework/recurrence-review"><img src="https://agentmods.dev/badge/skills/alejandro-ventures/llm-agnostic-icm-framework/recurrence-review/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/alejandro-ventures/llm-agnostic-icm-framework/recurrence-review"><img src="https://agentmods.dev/badge/skills/alejandro-ventures/llm-agnostic-icm-framework/recurrence-review.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.00063 | $0.00478 |
| Opus 5 | $0.00032 | $0.00239 |
| Sonnet 5 | $0.00013 | $0.00096 |
| Haiku 4.5 | $0.00006 | $0.00048 |
Grade A, and why
recurrence-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 10d 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.
What it actually says
Recurrence Review
Use only scripts/review.py; scheduled runs may invoke only scan.
Process
- Run
python workflows/recurrence-review/scripts/review.py scanfor a manual or scheduled review. - Report only newly created proposal paths. If status is
no_change, report that concisely. - For an open proposal, record
snoozed,rejected, orreopenedonly after explicit human approval usingdecide ... --approved. - Gate 1: run
scaffold <intent-key> --approvedonly after explicit same-turn approval. Keep the resulting workflow draft under this workflow'soutput/drafts/; do not edit the router. - Refine and validate the staged draft, then run
promotion-plan <intent-key>. Present the exact immutable plan path and hash. - Gate 2: run
promote <intent-key> --draft <path> --plan-hash <hash> --approvedonly after the user explicitly approves that hash in the same turn. Never commit, push, move, or delete.
Safety
- Read only schema-v2
scratchmetadata; never open raw scratch artifacts during scheduled scans. - Treat malformed JSON as a hard failure and create no proposal from an incomplete evidence set.
- Preserve proposals, decisions, drafts, promotion plans, and backups as immutable or append-only.
- Route every write through
_core/scripts/sandbox.pyand keep every artifact inside this workspace. - Append
output/run-log.csvand the token-tracker entry for every command.
What ships with it
1 file 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.
- 10d ago First seen · 37 lines · 63 tokens per session scan A 463679aef1fa
recurrence-review is a skill published in the GitHub repository alejandro-ventures/llm-agnostic-icm-framework (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 63 tokens to every session and 478 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
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
agent-engineering-expert
Build LLM agents that use tools safely: tool design, the agent loop, memory, MCP servers, multi-agent orchestration, sandboxing and prompt-injection defence. Use when the user mentions AI agents, tool use or function calling, MCP or Model Context Protocol, autonomous workflows, multi-agent systems, LangChain or…
junjo-evaluation
Turn a developer's product-quality objective into a complete Junjo Studio-backed evaluation workflow. Use when a coding agent needs to establish a baseline, design or generate typed cases, run or resume application-owned Node, Workflow, or Agent targets, inspect outcomes and exact trace evidence, compare a candidate…
junjo-openai-agents
Add Junjo's optional OpenAI Agents SDK integration to an application. Use when a coding agent needs to install junjo[openai-agents], expose a native Junjo Workflow or Agent as an OpenAI function tool, send standard OpenAI Agent and nested Junjo spans through one application-owned OpenTelemetry provider, declare an…
writing-workspace-jobs
Author FSM workspace jobs. Use when creating, editing, or debugging jobs, signals, or FSM workflows in workspace.yml.
workspace-api
Create, list, update, delete, and clean up workspaces via the daemon HTTP API at $FRIDAYDURL. Use when the user asks to create, edit, delete, or list workspaces, spaces, projects, or environments; add or patch signals / agents / jobs / memory / skills; convert a workspace.yml into a live workspace; wire up triggers…