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 ariadoss/superskills --skill toolsgit clone --depth 1 https://github.com/ariadoss/superskillsWrote 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/ariadoss/superskills/tools)<a href="https://agentmods.dev/skills/ariadoss/superskills/tools"><img src="https://agentmods.dev/badge/skills/ariadoss/superskills/tools/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/ariadoss/superskills/tools"><img src="https://agentmods.dev/badge/skills/ariadoss/superskills/tools.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.00082 | $0.01645 |
| Opus 5 | $0.00041 | $0.00822 |
| Sonnet 5 | $0.00016 | $0.00329 |
| Haiku 4.5 | $0.00008 | $0.00164 |
Grade A, and why
tools-page-generator 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 7d 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.
This is a copy
100% identical to tools-page-generator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pages: Tools (Free Tools)
Guides free tools pages that drive traffic and lead generation for the main product. Tools are free, standalone utilities — not the primary monetization. They serve the same ICP as the paid product, are often extracted mini-features from the full product (low dev effort), and typically scale via programmatic SEO. Distinct from features (paid capabilities) and resources (content hub).
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product, ICP, and conversion goals.
Identify:
- Tool types: Calculators, checkers, converters, generators (see Tool Types below)
- ICP alignment: Same audience as paid product; tools solve related problems
- Format: Single tool page vs. toolkit hub + per-tool pages
- Gate strategy: No signup (max traffic) vs. email gate (lead capture) vs. usage limits (taste → upgrade)
- Tech: Often SPA (single-page application); lightweight, fast load
Tools vs Features
| Dimension | Tools | Features |
|---|---|---|
| Monetization | Free; not primary revenue | Paid product capabilities |
| Purpose | Lead gen, traffic, trust | Conversion, evaluation |
| Content | Standalone utility; excerpt from product | Full product capability list |
| Scale | Many tools; programmatic keywords | Fewer, curated |
| Format | Often SPA; toolkit hub | Benefit-led grid/list |
| User intent | "I need to do X now" (task) | "What can this product do?" (evaluation) |
Tool Page Structure
| Section | Purpose |
|---|---|
| Headline | Task-focused; "Free [X] Checker" or "Calculate [Y] in Seconds" |
| Tool UI | Input → process → output; minimal friction |
| Instructions | 1–3 steps; "Enter URL → Click Analyze → Get Results" |
| Tool description | What it does, who it's for; SEO content |
| FAQ | Tool-specific: "What is [X]?", "How is [Y] calculated?" |
| CTA | "Get full access" / "Try [Product] free" — link to main product |
| Related tools | Internal links to other tools in toolkit |
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.
- 7d ago First seen · 129 lines · 82 tokens per session scan A 3439adefc381
tools-page-generator is a skill published in the GitHub repository ariadoss/superskills (9 stars, last pushed 5d ago), licensed MIT. It adds 82 tokens to every session and 1,645 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to tools-page-generator, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…