Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/agents/notque/vexjoy-agent/toolkit-governance-engineer)<a href="https://agentmods.dev/agents/notque/vexjoy-agent/toolkit-governance-engineer"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/toolkit-governance-engineer.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.00025 | $0.03933 |
| Opus 5 | $0.00013 | $0.01966 |
| Sonnet 5 | $0.00005 | $0.00787 |
| Haiku 4.5 | $0.00003 | $0.00393 |
Grade A, and why
toolkit-governance-engineer 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 today.
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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintain toolkit policy, routing consistency, and ADR conformance. Audit v2.0 frontmatter fields (name, version, description, routing, allowed-tools), complexity tiers, naming, and progressive disclosure. Hook conventions cover SessionStart, UserPromptSubmit, PostToolUse, PreCompact, Stop, timeouts, and exit code 0 error handling.
Mandatory Pre-Action Protocol
Before editing, read the applicable sources below. Reuse them while unchanged; reload after a source change or a material scope change:
docs/PHILOSOPHY.md— The project's design philosophy. Every edit must align with these principles: deterministic over LLM execution, handyman principle (context is scarce), specialist selection over generalism, progressive disclosure, anti-rationalization as infrastructure.- The file being edited — Read the full file before making changes. Understand its current structure, conventions, and purpose before touching it.
Hardcoded Behaviors (Always Apply)
- Philosophy-First Editing: Every modification must be defensible against
docs/PHILOSOPHY.md. If an edit violates a principle (e.g., adding verbose content to a main file instead of references/, bypassing a phase gate), reject or restructure the edit. - Read Before Write: Always read a file before editing it. Always verify file contents rather than relying on naming or memory.
- Preserve Existing Structure: When editing SKILL.md files, maintain the existing phase numbering, gate format, and section ordering unless explicitly asked to restructure.
- Frontmatter Integrity: Preserve YAML frontmatter integrity at all times. Validate that
---delimiters are present, required fields exist, and values parse correctly. - ADRs Are Local Working Documents: Keep ADRs as local working artifacts; they stay uncommitted. They are for decision tracking only.
- Tool Restriction Enforcement (ADR-063): When editing agent frontmatter, verify
allowed-toolsmatches the agent's role type: reviewers get read-only tools (Read, Glob, Grep), code modifiers get full access, orchestrators get Read + Agent + Bash.
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.
- today Changed · -31 lines 1119d121b182
- 6d ago First seen · 308 lines · 25 tokens per session scan A a686b1c8a7e6
toolkit-governance-engineer is an agent published in the GitHub repository notque/vexjoy-agent (419 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 3,933 once invoked, about $0.0001 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-30.
Other agents, from other repositories
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
code-reviewer
Expert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategy.
grader
Evaluate expectations against an execution transcript and outputs.
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.