brand-gen-verdict-unification

brand-gen-verdict-unification is a skill for Claude Code, Codex from velinussage/brand-gen. It costs 170 tokens per session (2,218 once invoked), scanned A, original, MIT.

A guide for combining the different quality checks in a brand-generation system into one consistent verdict format.

In plain words
What is it for?
Use it to catalogue verdict sources, map their outputs to one schema, and find places where separate review results are being merged into a single text field.
Why use it?
It addresses the problem of several review systems producing different decisions and storing them inconsistently, making results hard for later code to interpret.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to catalogue verdict sources, map their outputs to one schema, and find places where separate review results are being merged into a single text field.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/velinussage/brand-gen/brand-gen-verdict-unification
Install

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.

Any agent
npx skills add velinussage/brand-gen --skill brand-gen-verdict-unification
Clone the repo
git clone --depth 1 https://github.com/velinussage/brand-gen

Made for: Claude Code, Codex.

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 brand-gen-verdict-unification

README.md
[![agentmods](https://agentmods.dev/badge/skills/velinussage/brand-gen/brand-gen-verdict-unification/github.svg)](https://agentmods.dev/skills/velinussage/brand-gen/brand-gen-verdict-unification)
Your own site
<a href="https://agentmods.dev/skills/velinussage/brand-gen/brand-gen-verdict-unification"><img src="https://agentmods.dev/badge/skills/velinussage/brand-gen/brand-gen-verdict-unification/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 brand-gen-verdict-unification

Your own site · 80×15
<a href="https://agentmods.dev/skills/velinussage/brand-gen/brand-gen-verdict-unification"><img src="https://agentmods.dev/badge/skills/velinussage/brand-gen/brand-gen-verdict-unification.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 170 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,218 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.00170 $0.02218
Opus 5 $0.00085 $0.01109
Sonnet 5 $0.00034 $0.00444
Haiku 4.5 $0.00017 $0.00222

Measured 11d ago against content hash 858e61d79e46, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

brand-gen-verdict-unification 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 11d 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.

skills/brand-gen-verdict-unification/SKILL.md · 170 lines

How it starts

The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.

For Sage brand work in Pi, use the paste-ready prompt at docs/prompts/pi-sage-brand-gen-full-pipeline.md. Keep this link instead of copying the full prompt into skill bodies.

Brand-Gen Verdict Unification

Risk addressed: brand-gen has at least four parallel quality systems with non-fungible outputs, composed implicitly:

  1. card_engine._verify_render — file-level checks (PNG magic, headline presence) → gates visual_review_status to "render_suspect".
  2. DSPy BrandScorer (scoring/program.py) — rubric-based axis scoring with axis_scores, axis_rationales, decision: approved | iterate.
  3. vlm_critique — VLM gate with approved | rejected decision (legacy path).
  4. apply_generation_critique_policy (generation_flow.py) — policy mode (advisory vs strict), can block.
  5. build_structural_auto_critic (generation_flow.py:1016) — structural pre-flight critic.
  6. agent_review packet — orchestrator-level review record.

Each writes a different shape onto manifest entries. Naming is overloaded: "review" vs "critique" vs "critic" vs "feedback" are not consistently distinguished. There is no place where a downstream consumer can ask "what's the unified verdict for this version?" — they have to read 4-6 fields and apply implicit precedence.

What this skill produces

{
  "summary": {
    "verdict_emitters_total": 6,
    "manifest_fields_carrying_verdicts": 9,
    "implicit_combination_sites": 3,
    "conflicting_verdict_paths": 2,
    "naming_synonyms": ["review", "critique", "critic", "feedback", "verdict", "decision"]
  },
  "emitters": [
    {
      "emitter": "card_engine._verify_render",
      "site": "card_engine.py:1500-1540 (approx)",
      "verdict_shape": "{visual_review_status: 'pending' | 'render_suspect'}",
      "scope": "file-level (per PNG)",
      "blocking": false,
      "writes_to": ["manifest.entries[].visual_review_status"]
    },
    {
      "emitter": "BrandScorer.forward",
      "site": "scoring/program.py BrandScorer",
      "verdict_shape": "{axis_scores: {...}, axis_rationales: {...}, decision: 'approved' | 'iterate'}",
      "scope": "rubric-level (per version)",
      "blocking": false,
      "writes_to": ["review-packet.json", "manifest entry decision"]
    },
    {
      "emitter": "vlm_critique",
      "site": "vlm_critique.py",
      "verdict_shape": "{approved: bool, rationale: str}",
      "scope": "image-level (per version)",
      "blocking": false,
      "writes_to": ["iteration_memory positive/negative"]
    },
    {
      "emitter": "apply_generation_critique_policy",
      "site": "generation_flow.py apply_generation_critique_policy",
      "verdict_shape": "{policy_status: 'allow' | 'block', mode: 'advisory' | 'strict', findings: [...], bypassable: bool}",
      "scope": "policy-level (per run)",
      "blocking": true,
      "writes_to": ["pipeline_result.stop_reason", "run_ledger event"]
    },
    {
      "emitter": "build_structural_auto_critic",
      "site": "generation_flow.py:1016",
      "verdict_shape": "{P1: [...], P2: [...], P3: [...]}",
      "scope": "scratchpad-level (pre-execute)",
      "blocking": "indirect — drives iteration_memory negatives",
      "writes_to": ["iteration_memory negatives via auto_capture_generation_feedback"]
    },
    {
      "emitter": "agent_review",
      "site": "agent_review.py",
      "verdict_shape": "{orchestrator_review_packet: {...}}",
      "scope": "orchestration-level (per run)",
      "blocking": false,
      "writes_to": ["agent-review packet json"]
    }
  ],
  "implicit_combination_sites": [
    {
      "site": "manifest entry decision_field_resolution",
      "issue": "no documented rule for which verdict wins when render says render_suspect, scorer says approved, policy says allow"
    }
  ],
  "conflicting_verdict_paths": [
    {
      "scenario": "vlm_critique approved + apply_generation_critique_policy block",
      "current_behavior": "policy blocks the run; vlm verdict is recorded but does not gate",
      "documented": false
    }
  ],
  "recommended_verdict_schema": {
    "name": "Verdict",
    "fields": [
      "verdict_id",
      "version_id",
      "emitter: enum",
      "scope: enum",
      "decision: enum (approve | iterate | block | flag)",
      "blocking: bool",
      "rationale: str",
      "axis_scores: dict | null",
      "findings: list[Finding] | null",
      "supersedes: List[verdict_id]"
    ],
    "composition_rule": "blocking emitter (policy) > rubric (scorer) > image (vlm) > file (render verification) > pre-flight (auto-critic). Equal scope: most-recent supersedes older.",
    "manifest_field": "manifest.entries[].verdicts: List[Verdict]; manifest.entries[].resolved_verdict: Verdict (computed)"
  }
}

Read the full file on GitHub · 170 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. 11d ago First seen · 170 lines · 170 tokens per session scan A 858e61d79e46

Subscribe to this mod's changes

brand-gen-verdict-unification is a skill published in the GitHub repository velinussage/brand-gen (0 stars, last pushed 3mo ago), licensed MIT. It adds 170 tokens to every session and 2,218 once invoked, about $0.0009 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-31.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens