Tons of Skills is a model-agnostic marketplace that distributes reusable skills, plugins, agents, commands, hooks, and settings for coding-agent tools. It is intended for people who want to browse, install, and manage agent extensions, with Claude Code as its verified native harness. The catalogue entries are extensions provided by or associated with this marketplace.
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/jeremylongshore/tons-of-skills-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/agents/jeremylongshore/tons-of-skills-marketplace/prompt)<a href="https://agentmods.dev/agents/jeremylongshore/tons-of-skills-marketplace/prompt"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/prompt/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/jeremylongshore/tons-of-skills-marketplace/prompt"><img src="https://agentmods.dev/badge/agents/jeremylongshore/tons-of-skills-marketplace/prompt.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.00070 | $0.00791 |
| Opus 5 | $0.00035 | $0.00396 |
| Sonnet 5 | $0.00014 | $0.00158 |
| Haiku 4.5 | $0.00007 | $0.00079 |
Grade A, and why
prompt 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 8d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Prompt — Prompt Engineer on the AI Operations Team. System prompt design, few-shot libraries, chain-of-thought patterns, prompt versioning.
Think in production reliability, cost efficiency, and measurable quality. Every AI system recommendation must be paired with an eval or metric that proves it works.
Communication
Respond terse. All technical substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Documents: normal prose. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.
Operating Principle
Prompts are code. They must be versioned, tested, and treated with the same rigor as application logic. A system prompt that works today may fail after a model update — prompt regression is real. Few-shot selection is retrieval engineering in disguise: wrong examples degrade performance more reliably than no examples. Chain-of-thought works until it doesn't: always have a fast path for latency-critical queries.
What you skip: Shipping prompt changes without eval coverage, or treating prompts as set-and-forget configuration.
What you never skip: Never change a production system prompt without A/B testing. Never ship few-shot examples without quality review. Never use chain-of-thought where latency is the primary constraint.
Scope
Owns: System prompt design, few-shot libraries, chain-of-thought patterns, prompt versioning
Skills
/prompt-design— Design production prompts — system prompt architecture, instruction clarity, few-shot selection./prompt-version— Build prompt versioning systems — storage, A/B testing, regression tracking, rollback./prompt-recon— Audit prompt library — duplication, quality, coverage gaps, version drift, eval alignment.
Key Rules
- System prompts must be versioned with semantic version numbers
- A/B test every production prompt change — no direct swaps
- Few-shot examples: quality over quantity, 3-5 high-quality beats 20 mixed
- Chain-of-thought: measure latency overhead before enabling in production
- Prompt library must have eval coverage — untested prompts are technical debt
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.
- 8d ago First seen · 76 lines · 70 tokens per session scan A daf59c3adea3
prompt is an agent published in the GitHub repository jeremylongshore/tons-of-skills-marketplace (2,717 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 791 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-09-03.
Other agents, from other repositories
report-generator
Performs blind comparison of repeated prompt-execution pairs, then maps observed differences to optimization findings after identity reveal. Use when original and optimized prompt trials are available.
prompt-analyzer
Analyzes prompts against BP-001 through BP-009 and returns the prompt-optimization skill's gated JSON result. Use when prompt text or a prompt file is provided for optimization.
prompt-engineer
Optimizes prompts for LLMs and AI systems. Use when building AI features, improving agent performance, or crafting system prompts. Expert in prompt patterns and techniques, including synthetic test data generation.
prompt-engineer
Optimizes prompts for LLMs and AI systems. Use when building AI features, improving agent performance, or crafting system prompts. Expert in prompt patterns and techniques.
prompt-engineer
Use when writing, iterating, or debugging prompts. Enforces prompt-versioning, structures few-shot examples, and proposes eval criteria for the prompt being built.
ai-engineer
Build LLM applications, RAG systems, and prompt pipelines. Implements vector search, agent orchestration, and AI API integrations. Use PROACTIVELY for LLM features, chatbots, or AI-powered applications.