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 ezesubu/VERA --skill project-playbookgit clone --depth 1 https://github.com/ezesubu/VERAWrote 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/ezesubu/vera/project-playbook)<a href="https://agentmods.dev/skills/ezesubu/vera/project-playbook"><img src="https://agentmods.dev/badge/skills/ezesubu/vera/project-playbook/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/ezesubu/vera/project-playbook"><img src="https://agentmods.dev/badge/skills/ezesubu/vera/project-playbook.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.00000 | $0.00647 |
| Opus 5 | $0.00000 | $0.00324 |
| Sonnet 5 | $0.00000 | $0.00129 |
| Haiku 4.5 | $0.00000 | $0.00065 |
Grade A, and why
project-playbook 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 9d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PCW Studio knowledge
You are working inside PCW, Ezequiel's Unreal Engine project (an Aztec-themed
action game, with cyberpunk experiments). Treat the facts below as ground truth so
you don't rediscover them every session. When you learn something new and durable,
remember it (the Memory plugin) so this knowledge keeps growing.
Engine & frameworks
- The big project (PCWMaster) runs on a source-built engine at
E:/PCW/UnrealCore/UnrealEngine— not the Epic launcher build. Some launcher-only assumptions won't hold. - ACF (Advanced Character Framework) is the core gameplay framework for characters, combat, abilities and weapons. Prefer ACF patterns over hand-rolled ones.
- Niagara and Chaos Physics are active. GAS and Animation plugins are available but may be toggled off — check before assuming.
Known gotchas (don't relearn these)
- gFur is dead.
PCW-GFur_Advanced(and gFur generally) is abandoned and incompatible with UE5.7: it fails to compile, which yields a null material → SIGSEGV crash on mobile. This was the root cause of the mobile APK crash (same bug ~28×). Do NOT rely on gFur; re-materialize fur by hand with mobile-safe materials. - Mutable skeletons are transient. On PCWMaster, Mutable-generated characters have transient skeletons that bypass the asset registry — registry/asset-scan tools may not see them. Inspect the live actor instead of trusting a registry lookup.
- Mobile builds are the fragile path. PC PIE can be valid while the mobile build crashes. Always check mobile material/shader compatibility before packaging for Android (use the Mobile/Perf Doctor plugin if enabled).
Content conventions
- The Aztec bestiary scales Lv 1 → 10 (bosses like Huitzilopochtli, Tezcatlipoca, Tlacuache, etc.). Aztec/boss characters generally use the UE5 Manny skeleton.
- A clean "solo capture / showcase" lighting recipe (the S.A.M recipe): white directional light ~5.0, no shadows, exposure 1.0, bloom 0 — use it when capturing a single actor so renders come out in true color.
capture_actoruses a SceneCapture2D + show-only set, which sidesteps UE5.7's background-throttling problem for screenshots (the editor must otherwise have focus).
What ships with it
1 file 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.
- 9d ago First seen · 43 lines · 0 tokens per session scan A 152ec870f763
project-playbook is a skill published in the GitHub repository ezesubu/VERA (16 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 647 tokens. 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
game-development
Game development orchestrator. Routes to platform-specific skills based on project needs.
web-games
Web browser game development principles. Framework selection, WebGPU, optimization, PWA.
game-art
Game art principles. Visual style selection, asset pipeline, animation workflow.
game-audio
Game audio principles. Sound design, music integration, adaptive audio systems.
3d-games
3D game development principles. Rendering, shaders, physics, cameras.
game-design
Game design principles. GDD structure, balancing, player psychology, progression.