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/gebeer/processwire-ai-docs/processwire-agenttoolsnpx skills add gebeer/processwire-ai-docs --skill processwire-agenttoolsgit clone --depth 1 https://github.com/gebeer/processwire-ai-docsWhat 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.00040 | $0.00677 |
| Opus 5 | $0.00020 | $0.00338 |
| Sonnet 5 | $0.00008 | $0.00135 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
processwire-agenttools 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ProcessWire AgentTools
CLI access to the ProcessWire API and a file based migration system.
The module registers $at as a ProcessWire API variable (wire('at')).
Use the wrapper script as the default interface:
bash .agents/skills/processwire-agenttools/scripts/pw-at.sh ...
Commands
Run from the ProcessWire root directory (where index.php lives).
The wrapper auto-detects DDEV and runs inside the web container when appropriate.
It preserves Ryan's original AgentTools command model while adapting runtime details.
Do not call php index.php --at-* directly unless debugging the wrapper itself.
| Command | Purpose |
|---|---|
bash .agents/skills/processwire-agenttools/scripts/pw-at.sh eval 'CODE' |
Evaluate a PHP expression |
cat <<'PHP' | bash .agents/skills/processwire-agenttools/scripts/pw-at.sh stdin |
Evaluate multi-line PHP from stdin |
bash .agents/skills/processwire-agenttools/scripts/pw-at.sh cli |
Open interactive CLI session |
bash .agents/skills/processwire-agenttools/scripts/pw-at.sh migrations-apply |
Apply all pending migrations |
bash .agents/skills/processwire-agenttools/scripts/pw-at.sh migrations-list |
List migrations and their status |
bash .agents/skills/processwire-agenttools/scripts/pw-at.sh migrations-test |
Preview pending without applying |
Available API variables
All CLI modes and migrations share the same variables:
$pages, $templates, $fields, $fieldgroups, $modules, $config, $sanitizer, $users, $roles, $permissions, $session, $database, $cache, $log, $files, $at
When to use Migrations vs CLI
For one-off reads or changes, use the CLI. For environment-transferable changes, create a migration. Use cli only for multi-step interactive work.
| Operation | Default path | Reason |
|---|---|---|
| Queries, listing, inspecting | CLI | No state change to transfer |
| Templates, fields, fieldgroups | Migration | Schema should match across environments |
| Pages | Ask the user | Could be seed data or environment-specific |
| Module config, roles, permissions | Migration | Config drift causes subtle bugs |
| Debugging, testing | CLI | Throwaway by nature |
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 62 lines · 40 tokens per session scan A 6c3e789372ce
processwire-agenttools is a skill published in the GitHub repository gebeer/processwire-ai-docs (10 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 677 once invoked, about $0.0002 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.