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 gabrielmoreira/agent-skills-mirror --skill generate-prompt-requestgit clone --depth 1 https://github.com/gabrielmoreira/agent-skills-mirrorWrote 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/gabrielmoreira/agent-skills-mirror/generate-prompt-request)<a href="https://agentmods.dev/skills/gabrielmoreira/agent-skills-mirror/generate-prompt-request"><img src="https://agentmods.dev/badge/skills/gabrielmoreira/agent-skills-mirror/generate-prompt-request/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/gabrielmoreira/agent-skills-mirror/generate-prompt-request"><img src="https://agentmods.dev/badge/skills/gabrielmoreira/agent-skills-mirror/generate-prompt-request.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.00129 | $0.01133 |
| Opus 5 | $0.00064 | $0.00566 |
| Sonnet 5 | $0.00026 | $0.00227 |
| Haiku 4.5 | $0.00013 | $0.00113 |
Grade A, and why
generate-prompt-request 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 generate-prompt-request — 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Prompt Request
Overview
Turn the current working session into a compact "prompt request" one-pager for a pull request:
a single User: block that folds together every ask and every decision made during the session,
followed by a single Assistant: block summarizing what was actually built or done. It is a
one-pager a reviewer can read at a glance, not a turn-by-turn transcript.
When to use
- The user asks to "generate a prompt request", recap the session for a PR, or capture what was requested.
- Automatically while opening a pull request or writing a PR description. Generate this and include it in the PR body so reviewers see the asks and decisions behind the change. A repo's AGENTS.md or CLAUDE.md can wire this in with one line, for example: "When opening a PR, invoke the generate-prompt-request skill and include its output in the PR body."
Output format
Render the result INLINE in the reply. Do not write a file. Produce exactly this shape:
# <Session topic> — Prompt Request
**User:**
> <one consolidated request: all the asks first, then "Decisions made along the way: ..."
> folding in every choice the user made or approved>
**Assistant:**
> <a short summary of what was actually built or done, plus status>
How to build it
- Re-read the whole current session, from the first user message to now.
- Collect every distinct ask or requirement, and every decision the user made or approved, including ones that emerged mid-session (a stack choice, a "keep it simple" constraint, a dropped feature).
- Write ONE
User:block: a single natural request that compresses all of it. Lead with what they wanted, then end with "Decisions made along the way: ..." listing the resolved choices inline. - Write ONE
Assistant:block: a tight summary of what was delivered (what got built, its key properties, and status). Two to four sentences. - Title: derive it from the session's main deliverable (for example "White-Label Template — Prompt Request").
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 · 88 lines · 129 tokens per session scan A 77b62369500d
generate-prompt-request is a skill published in the GitHub repository gabrielmoreira/agent-skills-mirror (17 stars, last pushed yesterday), licensed MIT. It adds 129 tokens to every session and 1,133 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to generate-prompt-request, 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…