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 gebeer/processwire-ai-docs --skill create-pw-skillgit clone --depth 1 https://github.com/gebeer/processwire-ai-docsWrote 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/gebeer/processwire-ai-docs/create-pw-skill)<a href="https://agentmods.dev/skills/gebeer/processwire-ai-docs/create-pw-skill"><img src="https://agentmods.dev/badge/skills/gebeer/processwire-ai-docs/create-pw-skill/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/gebeer/processwire-ai-docs/create-pw-skill"><img src="https://agentmods.dev/badge/skills/gebeer/processwire-ai-docs/create-pw-skill.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.00053 | $0.00667 |
| Opus 5.5 | $0.00021 | $0.00267 |
| Sonnet 5.5 | $0.00011 | $0.00133 |
| Haiku 4.5 | $0.00005 | $0.00067 |
Grade A, and why
create-pw-skill 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 1mo 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create ProcessWire Skill
Workflow for creating a new ProcessWire agent skill from source material.
Checklist
Copy and track progress:
- [ ] 1. Gather sources
- [ ] 2. Scope content with user
- [ ] 3. Read best practices
- [ ] 4. Propose file structure
- [ ] 5. Draft description
- [ ] 6. Create skill files
- [ ] 7. Output summary
Workflow
1. Gather sources
Read all paths and URLs provided in $ARGUMENTS. Accept: file paths, directory paths, URLs (module docs, blog posts, API source code). If no arguments provided, ask the user for source material.
2. Scope content
Ask the user: extract all content from sources, or focus on specific parts? Wait for answer before proceeding.
3. Read best practices
Fetch and read the skill authoring best practices: https://platform.claude.com/docs/en/agents-and-tools/agent-skills/best-practices
Focus on: description format, progressive disclosure, line limits, file structure.
4. Propose file structure
Study existing skills in skills/ for conventions. Then propose a directory layout:
skills/processwire-[name]/
├── SKILL.md # Overview + quick start + reference links
├── [topic-a].md # Reference file per major topic
└── [topic-b].md # ...
Present to user for approval. Do not proceed until approved.
5. Draft description
Draft the YAML description field:
- Third-person verb phrases (Creates, Manages, Generates...)
- Include specific trigger terms and keywords for discovery
- End with "Use when..." clause listing concrete scenarios
- Max 1024 characters
Show description to user for review before proceeding.
6. Create skill files
Create the skill directory and files under skills/.
Rules:
- Naming:
processwire-*(lowercase, hyphens only) - SKILL.md body: under 500 lines, aim for 50-70
- Reference files: one level deep from SKILL.md, descriptive filenames
- Table of contents required in files over 100 lines
- Code examples: always include
namespace ProcessWire - Do NOT include knowledge the assistant already has (basic PHP, general programming)
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.
- 1mo ago First seen · 95 lines · 53 tokens per session scan A 64fcee7fdbe5
create-pw-skill is a skill published in the GitHub repository gebeer/processwire-ai-docs (11 stars, last pushed 4mo ago), licensed MIT. It adds 53 tokens to every session and 667 once invoked, about $0.0002 per session on Opus 5.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
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…
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…
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…