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 jimmc414/claude-code-plugin-marketplace --skill cache-recursive-callsgit clone --depth 1 https://github.com/jimmc414/claude-code-plugin-marketplaceWrote 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/jimmc414/claude-code-plugin-marketplace/cache-recursive-calls)<a href="https://agentmods.dev/skills/jimmc414/claude-code-plugin-marketplace/cache-recursive-calls"><img src="https://agentmods.dev/badge/skills/jimmc414/claude-code-plugin-marketplace/cache-recursive-calls.svg" alt="Measured on agentmods" 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.00028 | $0.00661 |
| Opus 5 | $0.00014 | $0.00331 |
| Sonnet 5 | $0.00006 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
Grade A, and why
cache-recursive-calls 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 6d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cache-recursive-calls
When to Use
- Recursive function computes same inputs multiple times
- Overlapping subproblems (DP)
- Fibonacci-like recurrence relations
- Tree/graph traversal with revisits
- Expensive pure functions called repeatedly
When NOT to Use
- Function has side effects
- Inputs aren't hashable
- Cache would grow too large
- Each input computed only once
The Pattern
Use @functools.cache (Python 3.9+) or @functools.lru_cache(None) to memoize.
from functools import cache
@cache
def fib(n):
"""Fibonacci with memoization: O(n) instead of O(2^n)."""
if n <= 1:
return n
return fib(n - 1) + fib(n - 2)
# Or with size limit
from functools import lru_cache
@lru_cache(maxsize=1000)
def expensive_lookup(key):
# ... expensive computation
return result
Example (from pytudes)
from functools import cache
# TSP with dynamic programming (TSP.ipynb)
@cache
def shortest_segment(A, Bs, C):
"""Shortest path from A through all cities in Bs to C."""
if not Bs:
return [A, C]
return min(
(shortest_segment(A, Bs - {B}, B) + [C] for B in Bs),
key=segment_length
)
# Key insight: Bs must be frozenset (hashable)
cities = frozenset(['NYC', 'LA', 'CHI', 'HOU'])
tour = shortest_segment('START', cities, 'START')
# Expression counting (Countdown.ipynb)
@cache
def expressions(numbers):
"""All expressions makeable from numbers."""
if len(numbers) == 1:
return {numbers[0]: str(numbers[0])}
table = {}
for Lnums, Rnums in splits(numbers):
for L, R in product(expressions(Lnums), expressions(Rnums)):
for op in ops:
# Combine L and R with op
...
return table
# Word segmentation (ngrams.py)
@cache
def segment(text):
"""Best word segmentation of text."""
if not text:
return []
candidates = ([first] + segment(rest)
for first, rest in splits(text))
return max(candidates, key=word_probability)
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.
- 6d ago First seen · 96 lines · 28 tokens per session scan A a978de98bfca
cache-recursive-calls is a skill published in the GitHub repository jimmc414/claude-code-plugin-marketplace (4 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 661 once invoked, about $0.0001 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
ai-ml-development
AI and machine learning development with PyTorch, TensorFlow, and LLM integration. Use when building ML models, training pipelines, fine-tuning LLMs, or implementing AI features.
codexer
Python research assistant with Context7 MCP. Use for Python library research, evaluating packages, enforcing strict Python coding standards, or fetching up-to-date library docs via Context7.
fastapi
Skill "fastapi" from ashish7802/awesome-api-skills, covering fastapi skill, ecosystem graph, quick start, production patterns and dependency injection.
python-packaging
Configure Python package metadata, setup.py, and pyproject.toml for distribution using UV or setuptools. Use when setting up Python packages, configuring build systems, or preparing projects for PyPI publication.
analyzing-windows-prefetch-with-python
Parse Windows Prefetch files using the windowsprefetch Python library to reconstruct application execution history, detect renamed or masquerading binaries, and identify suspicious program execution patterns.
clean-code
Use when the user writes new Python, or asks for review, refactor, or cleanup of Python code, names, comments/docstrings, functions, or tests. Applies Robert Martin's complete Clean Code catalog -- naming, functions, comments, DRY, boundary conditions, and tests -- to the code being changed.