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 matteocervelli/llms --skill recursive-communicatorgit clone --depth 1 https://github.com/matteocervelli/llmsWrote 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/matteocervelli/llms/recursive-communicator)<a href="https://agentmods.dev/skills/matteocervelli/llms/recursive-communicator"><img src="https://agentmods.dev/badge/skills/matteocervelli/llms/recursive-communicator/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/matteocervelli/llms/recursive-communicator"><img src="https://agentmods.dev/badge/skills/matteocervelli/llms/recursive-communicator.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.00029 | $0.04430 |
| Opus 5.5 | $0.00012 | $0.01772 |
| Sonnet 5.5 | $0.00006 | $0.00886 |
| Haiku 4.5 | $0.00003 | $0.00443 |
Grade A, and why
recursive-communicator 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 — 635 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
The recursive-communicator skill provides structured protocols for managing recursive communication loops between the validation orchestrator, validation specialists, and the main feature implementer agent. It handles failure notifications, fix requests, re-validation triggers, and loop termination to ensure validation issues are resolved systematically.
When to Use
This skill auto-activates when you:
- Communicate validation failures to the main agent
- Request fixes from the main agent for validation issues
- Trigger re-validation after main agent fixes
- Manage recursive fix loops (failure → fix → re-check → repeat)
- Track iteration counts in recursive communication
- Prevent deadlocks in recursive loops
- Escalate unresolvable validation issues
- Log communication history for traceability
Provided Capabilities
1. Failure Communication
- Structured Failure Reports: Format validation failures for main agent
- Detailed Error Information: Include file locations, line numbers, error messages
- Suggested Fixes: Provide specialist recommendations for resolving issues
- Priority Tagging: Mark critical vs. non-critical failures
- Context Preservation: Include all relevant context for debugging
2. Fix Request Management
- Clear Fix Requests: Explicitly request main agent to fix specific issues
- Action Items: Provide actionable list of fixes needed
- Deadline Awareness: Track iteration limits (max 5)
- Fix Verification: Confirm when main agent completes fixes
- Re-validation Triggering: Signal specialists to re-check after fixes
3. Re-validation Coordination
- Re-check Signals: Trigger specialist re-validation after fixes
- Iteration Tracking: Increment and track iteration counts
- Status Updates: Communicate re-validation status to all parties
- Loop Continuation: Determine if another iteration needed
- Loop Termination: Identify when to exit recursive loop
4. Deadlock Prevention
- Max Iteration Limits: Enforce maximum 5 iterations per specialist
- Timeout Detection: Identify stalled communication
- Escalation Triggers: Escalate after max iterations or timeout
- User Intervention Requests: Flag when human input needed
- Graceful Degradation: Handle unresolvable issues without blocking workflow
What ships with it
2 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.
- 1mo ago First seen · 635 lines · 29 tokens per session scan A 9c79a7ce5864
recursive-communicator is a skill published in the GitHub repository matteocervelli/llms (25 stars, last pushed 5mo ago), licensed MIT. It adds 29 tokens to every session and 4,430 once invoked, about $0.0001 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-09-01.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.