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 verify-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/verify-pw-skill)<a href="https://agentmods.dev/skills/gebeer/processwire-ai-docs/verify-pw-skill"><img src="https://agentmods.dev/badge/skills/gebeer/processwire-ai-docs/verify-pw-skill.svg" alt="Measured on agentmods" 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.00058 | $0.00732 |
| Opus 5 | $0.00029 | $0.00366 |
| Sonnet 5 | $0.00012 | $0.00146 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade A, and why
verify-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 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.
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.
Verify ProcessWire Skill
Verify an existing ProcessWire skill's accuracy and best practices compliance against source material.
Input
Accepts either:
- Same session: output from
/create-pw-skill(sources + file structure already in context) - Manual: skill path + source paths/URLs via $ARGUMENTS
If neither available, ask the user for the skill path and source material.
Checklist
Copy and track progress:
- [ ] 1. Identify inputs
- [ ] 2. Read best practices
- [ ] 3. Run parallel verification
- [ ] 4. Compile issue table
- [ ] 5. Present to user
- [ ] 6. Apply approved fixes
Workflow
1. Identify inputs
Determine the skill directory and list its files (SKILL.md + reference files). Confirm all source material (paths, URLs) with the user.
2. Read best practices
Fetch and read: https://platform.claude.com/docs/en/agents-and-tools/agent-skills/best-practices
Focus on: description format, progressive disclosure, line limits, file structure, naming conventions.
3. Run parallel verification
Launch one subagent per reference file. Each subagent reads its file and the relevant source material, checking three dimensions:
Accuracy
- Method signatures match source (argument names, order, types)
- Property names and values are correct
- Code syntax is valid (
namespace ProcessWire, correct API patterns) - No contradictions with source
Coverage
- Important features present in source but missing from skill
- Missing common patterns or pitfalls documented in source
Best practices
- SKILL.md is lean overview with progressive disclosure to reference files
- Description: third-person verbs, trigger terms, "Use when..." clause
- SKILL.md body under 500 lines
- Table of contents in files over 100 lines
- Reference files one level deep, descriptive filenames
- No info the assistant already knows (basic PHP, etc.)
Also verify SKILL.md frontmatter (name matches directory, description under 1024 chars).
4. Compile issue table
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 · 95 lines · 58 tokens per session scan A d366800097ee
verify-pw-skill is a skill published in the GitHub repository gebeer/processwire-ai-docs (10 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 732 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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…