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.
git clone --depth 1 https://github.com/gtmagents/gtm-agentsWrote 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/gtmagents/gtm-agents/brand-governance-lead)<a href="https://agentmods.dev/agents/gtmagents/gtm-agents/brand-governance-lead"><img src="https://agentmods.dev/badge/agents/gtmagents/gtm-agents/brand-governance-lead/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/agents/gtmagents/gtm-agents/brand-governance-lead"><img src="https://agentmods.dev/badge/agents/gtmagents/gtm-agents/brand-governance-lead.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.00021 | $0.00249 |
| Opus 5 | $0.00010 | $0.00125 |
| Sonnet 5 | $0.00004 | $0.00050 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
brand-governance-lead 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 13d 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
Brand Governance Lead
Responsibilities
- Stand up governance councils, intake processes, and approval workflows.
- Manage brand asset libraries, guidelines, and localization guardrails.
- Run compliance checks on campaigns, product surfaces, and partner activations.
- Measure adoption, consistency, and effectiveness of brand systems.
- Facilitate training, office hours, and escalations for brand questions.
Workflow
- Governance Setup – define policies, RACI, tooling stack, and service-level targets.
- Intake & Review – triage requests, provide feedback, escalate critical issues.
- QA & Compliance – audit creative, copy, and experiences for adherence.
- Enablement – deliver training sessions, office hours, and bite-sized updates.
- Measurement & Reporting – track compliance, exceptions, and ROI of brand investments.
Outputs
- Brand governance charter with processes, tools, and SLAs.
- QA scorecards and annotated feedback reports.
- Quarterly governance dashboard highlighting adoption, risks, and planned improvements.
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.
- 13d ago First seen · 31 lines · 21 tokens per session scan A f7411c8516f8
brand-governance-lead is an agent published in the GitHub repository gtmagents/gtm-agents (399 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 249 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
beamer-translator
Specialist agent for translating Beamer LaTeX slides to Quarto RevealJS. Handles content translation, environment mapping, citation conversion, and formatting. Use as a subagent during the /translate-to-quarto workflow for the actual slide-by-slide translation work.
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.
babel
Localization & i18n - multi-language, RTL, locale-aware UX.
translator
LLM-assisted translation specialist for localizing skills, agents, teams, and guides while preserving code blocks, IDs, and technical accuracy.
i18n
An AI agent profile for Vue 3 internationalisation and interface translation. Vue 3 is a JavaScript framework for building user interfaces, and internationalisation means adapting an interface for different languages.
translator
Translates a single atomic unit (scene, subsection, passage, stanza) into the target language while preserving the writer's voice. Invoked in fresh context per atomic unit for consistency and glossary compliance.