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 agentmods add skills/shawnstack/quickforge/documentsnpx skills add shawnstack/quickforge --skill documentsgit clone --depth 1 https://github.com/shawnstack/quickforgeWhat 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 | $0.00050 | $0.00898 |
| Opus 5 | $0.00025 | $0.00449 |
| Sonnet 5 | $0.00010 | $0.00180 |
| Haiku 4.5 | $0.00005 | $0.00090 |
Grade A, and why
documents 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 2d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documents skill
Use this skill to produce high-quality document deliverables in QuickForge. A document deliverable should be useful as a standalone artifact: clear structure, accurate content, appropriate tone, and enough polish that the user can copy, publish, or hand it off.
This QuickForge adaptation intentionally does not depend on Codex cache paths, Codex workspace dependencies, or @oai/artifact-tool. Prefer Markdown and plain-text deliverables first. If the user explicitly needs DOCX/PDF/export automation, explain the available local workflow and ask before using shell commands or external converters.
When to use
Use this skill for requests involving:
- Drafting reports, proposals, memos, specs, essays, documentation, README files, knowledge-base articles, manuals, policies, or meeting notes.
- Improving, restructuring, proofreading, translating, or summarizing an existing document.
- Creating DOCX-oriented content, even if the final QuickForge deliverable is initially Markdown.
- Turning raw notes, transcripts, bullet points, or source files into a polished document.
- Creating templates, outlines, style guides, checklists, or editorial feedback.
Do not use this skill for code-only tasks unless the requested output is a document about code.
Output principles
- Clarify the deliverable shape only when necessary. If the requested format is obvious, start directly.
- Choose a structure before writing. For non-trivial documents, create a short outline internally, then draft.
- Preserve user intent and constraints. Match requested tone, language, audience, length, and format.
- Separate facts from assumptions. If source material is incomplete, say what you inferred.
- Make the document scannable. Use headings, bullets, tables, callouts, and summaries where helpful.
- Avoid filler. Prefer concise, useful content over generic prose.
- Cite or reference sources when the user provides them. Do not invent citations.
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.
- 2d ago First seen · 97 lines · 50 tokens per session scan A 9f8b9a24c064
documents is a skill published in the GitHub repository shawnstack/quickforge (47 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 898 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
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…