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/ezesubu/vera/project-intelligencenpx skills add ezesubu/VERA --skill project-intelligencegit 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-intelligence)<a href="https://agentmods.dev/skills/ezesubu/vera/project-intelligence"><img src="https://agentmods.dev/badge/skills/ezesubu/vera/project-intelligence.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 | $0.00000 | $0.00268 |
| Opus 5 | $0.00000 | $0.00134 |
| Sonnet 5 | $0.00000 | $0.00054 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
project-intelligence 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 4d 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.
What it actually says
Project Intelligence
VERA ships with project-intelligence tools that read the project straight from disk (no editor bridge required). Use them to ground your reasoning in what actually exists before you propose changes.
Tools
-
analyze_project— Get an overview of the project: which engine it targets, which plugins are active, which are available to enable, which are missing, and a high-level asset overview. Call this BEFORE reasoning about the project or proposing changes (e.g. adding features, enabling plugins, planning work), so your conclusions match reality instead of assumptions. -
find_asset— Locate an asset by name. Pass a (partial, case-insensitive)nameand get back matching/Game/...-style content paths. Use this when you need to confirm an asset exists or find its exact path before referencing it.
Notes
- Both tools reflect the on-disk project as it is right now. They do not need the editor to be running.
- Combine these findings with your memory: when
analyze_projectsurfaces something notable (a missing plugin, an unusual engine version, a large asset library), remember it so you don't have to re-discover it every session.
What ships with it
3 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.
- 4d ago First seen · 26 lines · 0 tokens per session scan A 8f8f357f383f
project-intelligence is a skill published in the GitHub repository ezesubu/VERA (15 stars, last pushed 25d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 268 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.
3d-games
3D game development principles. Rendering, shaders, physics, cameras.
game-design
Game design principles. GDD structure, balancing, player psychology, progression.
multiplayer
Multiplayer game development principles. Architecture, networking, synchronization.
pc-games
PC and console game development principles. Engine selection, platform features, optimization strategies.