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 Tenstu/Pass-LLM-with-LLM --skill solve-skeletongit clone --depth 1 https://github.com/Tenstu/Pass-LLM-with-LLMWrote 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/tenstu/pass-llm-with-llm/solve-skeleton)<a href="https://agentmods.dev/skills/tenstu/pass-llm-with-llm/solve-skeleton"><img src="https://agentmods.dev/badge/skills/tenstu/pass-llm-with-llm/solve-skeleton/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/tenstu/pass-llm-with-llm/solve-skeleton"><img src="https://agentmods.dev/badge/skills/tenstu/pass-llm-with-llm/solve-skeleton.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.00198 | $0.01979 |
| Opus 5.5 | $0.00079 | $0.00792 |
| Sonnet 5.5 | $0.00040 | $0.00396 |
| Haiku 4.5 | $0.00020 | $0.00198 |
Grade A, and why
solve-skeleton 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solve Skeleton Skill
Bare-bones Python solve() skeletons for ACM/OJ problems. No logic inside — only structure,
I/O plumbing, and TODO markers. After filling TODOs, use the algo-annotation skill to add
Chinese comments and # [防错] markers.
1. Core Convention
I/O
input = sys.stdin.readline
n = int(input())
nums = list(map(int, input().split()))
For strings: s = input().strip(). For output: print(ans) or print("\n".join(out)).
Never use sys.stdin.buffer, iter(data) + next(it), or .buffer.read().split().
Stage Separator
Five dashes, 58 equal signs. No trailing content.
# ============================================================
5-Phase Structure
Every solve() follows this layout:
def solve():
"""Input format: ...
Output format: ...
"""
input = sys.stdin.readline
# ============================================================
# Preprocess
# ============================================================
# ============================================================
# Algorithm
# ============================================================
# ============================================================
# Output
# ============================================================
if __name__ == "__main__":
solve()
The docstring must state input and output format — this is the contract with the grader.
2. Anti-Pattern Checklist
Never do these when writing a skeleton. They cause WA/TLE that are hard to debug.
- No
sys.stdin.buffer— returns bytes, requires.decode(), breaks on mixed string/numeric input. - No
input()without alias — bareinput()is slow on large data; alwaysinput = sys.stdin.readline. - No
list.pop(0)in BFS — usedeque.popleft()or you get O(n²) per pop. - No recursive
find()in DSU — Python recursion limit (~1000) causes RecursionError on deep chains. Use iterative find with path compression. - No missing 0-based conversion — if input is 1-based, subtract 1 immediately after reading.
- No
.strip()omission on string reads —input().strip()removes trailing\n;input()includes it. - No forgetting
if __name__ == "__main__"— some OJ platforms require the guard. - No stale heap entries in Dijkstra — always skip with
if d != dist[u]: continue.
What ships with it
3 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 · 139 lines · 198 tokens per session scan A 4cb98febc3d7
solve-skeleton is a skill published in the GitHub repository Tenstu/Pass-LLM-with-LLM (5 stars, last pushed 3mo ago), licensed MIT. It adds 198 tokens to every session and 1,979 once invoked, about $0.0008 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 skills, from other repositories
django-patterns
Django architecture patterns, REST API design with DRF, ORM best practices, caching, signals, middleware, and production-grade Django apps.
accelerate
Run PyTorch training across GPUs with minimal changes.
python-patterns
Python-specific design patterns and best practices including protocols, dataclasses, context managers, decorators, async/await, type hints, and package organization. Use when working with Python code to apply Pythonic patterns.
python-testing
Python testing best practices using pytest including fixtures, parametrization, mocking, coverage analysis, async testing, and test organization. Use when writing or improving Python tests.
pytorch-patterns
PyTorch deep learning patterns and best practices for building robust, efficient, and reproducible training pipelines, model architectures, and data loading.
fastapi-patterns
FastAPI patterns for async APIs, dependency injection, Pydantic request and response models, OpenAPI docs, tests, security, and production readiness.