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 imartinstudio/cover-prompt-skills --skill cover-tipsgit clone --depth 1 https://github.com/imartinstudio/cover-prompt-skillsWrote 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/imartinstudio/cover-prompt-skills/cover-tips)<a href="https://agentmods.dev/skills/imartinstudio/cover-prompt-skills/cover-tips"><img src="https://agentmods.dev/badge/skills/imartinstudio/cover-prompt-skills/cover-tips/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/imartinstudio/cover-prompt-skills/cover-tips"><img src="https://agentmods.dev/badge/skills/imartinstudio/cover-prompt-skills/cover-tips.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.00061 | $0.01224 |
| Opus 5 | $0.00030 | $0.00612 |
| Sonnet 5 | $0.00012 | $0.00245 |
| Haiku 4.5 | $0.00006 | $0.00122 |
Grade A, and why
cover-tips 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 12d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CoverTips
cover-tips is a two-stage selector. It preserves the user's original request,
confirmed style, and confirmed asset scope, then hands the request to the
selected skill. It is a routing boundary only: it does not own visual-style
rules, style defaults, or generic prompt generation.
Stage 1: Confirm the visual style
- If the user has named a supported style, identify its route ID and continue to Stage 2. Do not generate a cover, template, or prompt at this stage.
- If the user has not named a style, give 1–3 candidates from the request's subject, use case, and explicit constraints. Show each candidate's display name, route ID, and a short reason grounded in the request. Ask the user to confirm one candidate. Do not silently select a style or call a target skill.
- If the request names an unsupported style, say that no matching route is available and ask the user to choose from the supported route IDs. Never silently substitute another style.
When the user has already made the asset scope explicit, use that information
to constrain the candidate list: an article package may only propose the four
styles with a published with-docs route. Otherwise, keep the style choice
separate from the asset-scope question in Stage 2.
Supported style route IDs
The following table is an inventory of route IDs, not a copy of any style's visual rules.
| Display name | Single-cover route | Article-package route |
|---|---|---|
| 3D Eye | cover-3d-eye |
cover-3d-eye-with-docs |
| Anthropic Research Editorial | cover-anthropic-research |
— |
| Black-White Minimal | cover-black-white-minimal |
— |
| Budapest Poster | cover-budapest-poster |
— |
| Cream Orange Knowledge Poster | cover-cream-orange-knowledge-poster |
cover-cream-orange-knowledge-poster-with-docs |
| Editorial Collage | cover-editorial-collage |
— |
| Giant Perspective Poster | cover-giant-perspective-poster |
— |
| Light Product | cover-light-product |
cover-light-product-with-docs |
| McKinsey Briefing Style | cover-mckinsey-briefing-style |
— |
| Midnight Studio | cover-midnight-studio |
— |
| Sketch Knowledge Poster | cover-sketch-knowledge-poster |
cover-sketch-knowledge-poster-with-docs |
| Tea Oriental | cover-tea-oriental |
— |
| Trendy Color Poster | cover-trendy-color-poster |
— |
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.
- 12d ago First seen · 111 lines · 61 tokens per session scan A 99790d340fe9
cover-tips is a skill published in the GitHub repository imartinstudio/cover-prompt-skills (9 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 1,224 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-08-31.
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…