toolkit-governance-engineer

toolkit-governance-engineer is an agent for Claude Code from notque/vexjoy-agent. It costs 25 tokens per session (3,870 once invoked), scanned A, original, MIT.

An operator for maintaining an internal toolkit of coding-agent instructions. It manages skills, routing tables that choose instructions for requests, architecture decision records, hooks, and index files.

In plain words
What is it for?
Use it to edit skills, update routing rules, manage decision records, regenerate coverage indexes, standardize hooks, and check frontmatter.
Why use it?
It keeps the toolkit’s instructions consistent and complete as they change. It also helps prevent broken routing, missing registrations, and invalid instruction metadata.

Agent for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions Claude Code.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 scripts/validate-references.py --agent {agent-name}.

Good fit Use it to edit skills, update routing rules, manage decision records, regenerate coverage indexes, standardize hooks, and check frontmatter.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/notque/vexjoy-agent
agentmods
npx agentmods add agents/notque/vexjoy-agent/toolkit-governance-engineer

Made for: Claude Code.

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.

agentmods badge for toolkit-governance-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/notque/vexjoy-agent/toolkit-governance-engineer/github.svg)](https://agentmods.dev/agents/notque/vexjoy-agent/toolkit-governance-engineer)
Your own site
<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/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.

agentmods 80×15 button for toolkit-governance-engineer

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,870 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00025 $0.03870
Opus 5.5 $0.00010 $0.01548
Sonnet 5.5 $0.00005 $0.00774
Haiku 4.5 $0.00003 $0.00387

Measured 5d ago against content hash 8860872a4c9a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 5d 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.

agents/toolkit-governance-engineer.md · 275 lines

How it starts

The opening of the file, as written. The whole thing — 275 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:

  1. docs/PHILOSOPHY.md — The project's frontend 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.
  2. 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-tools matches the agent's role type: reviewers get read-only tools (Read, Glob, Grep), code modifiers get full access, orchestrators get Read + Agent + Bash.

Read the full file on GitHub · 275 lines

Changes

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.

  1. 5d ago Changed 8860872a4c9a
  2. 1mo ago Changed be6408f986f4
  3. 1mo ago Changed · -2 lines c555236f21fb
  4. 1mo ago Changed · -31 lines 1119d121b182
  5. 1mo ago First seen · 308 lines · 25 tokens per session scan A a686b1c8a7e6

Subscribe to this mod's changes

toolkit-governance-engineer is an agent published in the GitHub repository notque/vexjoy-agent (442 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 3,870 once invoked, about $0.0001 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-30.