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 keodubo/PAW-Wiki --skill paw-feature-mastergit clone --depth 1 https://github.com/keodubo/PAW-WikiWrote 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/keodubo/paw-wiki/paw-feature-master)<a href="https://agentmods.dev/skills/keodubo/paw-wiki/paw-feature-master"><img src="https://agentmods.dev/badge/skills/keodubo/paw-wiki/paw-feature-master/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/keodubo/paw-wiki/paw-feature-master"><img src="https://agentmods.dev/badge/skills/keodubo/paw-wiki/paw-feature-master.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.00062 | $0.01744 |
| Opus 5.5 | $0.00025 | $0.00698 |
| Sonnet 5.5 | $0.00012 | $0.00349 |
| Haiku 4.5 | $0.00006 | $0.00174 |
Grade A, and why
paw-feature-master 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 2mo 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Paw Feature Master
Overview
Use this as the entrypoint for PAW/Forkd work. It keeps implementation aligned with the checkout, PAW-Wiki, Maven layer boundaries, and the user's preference for safe, reversible changes.
Required First Pass
- Resolve the PAW app checkout. Prefer the current working directory; otherwise use
PAW_APP_REPOif set, or ask for the path. - Read
<PAW_APP_REPO>/CLAUDE.md. - Read
<PAW_APP_REPO>/PAW-Wiki/docs/CLAUDE.mdwhen the wiki is vendored beside the app; otherwise read the cloned PAW-Wiki repo'sdocs/CLAUDE.md. - Read the corresponding
docs/index.md. - Resolve the project stage:
TP1,TP2, orTP final. Use the user's explicit stage if provided; otherwise infer only when the task is unambiguous. Ask before changing stack assumptions. - Read the current code and tests for the affected flow before trusting older plans.
- For substantial work, show a short plan before editing.
Use references/project-map.md for the current module map, canonical wiki pages, feature categories, and verification gates.
Stage Routing
- TP1: Keep the classic stack: Spring Web MVC, JSP/JSTL, JDBC, HSQLDB, Spring Security, Logback, Maven WAR. Do not introduce JPA/Hibernate, SPA, REST-only architecture, or frontend build tooling unless the user explicitly asks.
- TP2/TPE2: Treat work as persistence migration or Hibernate/JPA adaptation when it touches entities,
EntityManager, ORM config, fetch/cascade behavior, data/schema migration, TPE1 feedback corrections, or JDBC-to-JPA DAO changes. Use$paw-tp2-migrationbefore layer skills for migration planning or implementation. - TP final: Treat work as REST + SPA migration when the user explicitly says
TP final, final delivery,pasalo al final, REST/SPA/API/frontend migration, or when it touches Jersey/JAX-RS/resources, DTO API contracts, Basic/Bearer stateless auth, refresh tokens, frontend module/build, routing, client state, cache/file revving, base path, WAR packaging, or static hosting. Use$paw-tp-final-migrationbefore layer skills for migration planning or implementation.
What ships with it
2 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.
- 2mo ago First seen · 96 lines · 62 tokens per session scan A 654e2da27c03
paw-feature-master is a skill published in the GitHub repository keodubo/PAW-Wiki (10 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 1,744 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
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…