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 skills add velinussage/brand-gen --skill brand-gen-loop-shape-assessmentgit clone --depth 1 https://github.com/velinussage/brand-genWrote 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/velinussage/brand-gen/brand-gen-loop-shape-assessment)<a href="https://agentmods.dev/skills/velinussage/brand-gen/brand-gen-loop-shape-assessment"><img src="https://agentmods.dev/badge/skills/velinussage/brand-gen/brand-gen-loop-shape-assessment/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/skills/velinussage/brand-gen/brand-gen-loop-shape-assessment"><img src="https://agentmods.dev/badge/skills/velinussage/brand-gen/brand-gen-loop-shape-assessment.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.00171 | $0.01976 |
| Opus 5.5 | $0.00068 | $0.00790 |
| Sonnet 5.5 | $0.00034 | $0.00395 |
| Haiku 4.5 | $0.00017 | $0.00198 |
Grade A, and why
brand-gen-loop-shape-assessment 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 146 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 Loop-Shape Assessment
Risk addressed: the route → plan → critique → scratchpad → generate flow is a sequential mutation pipeline, not a feedback graph. Each phase reads the previous JSON file and writes a new one. Critique is in-line and one-shot (pipeline_runner._run_critique); it cannot iterate the plan. Auto-feedback writes to iteration_memory which is read at next-run prompt assembly time. There is no in-flight "the critique fixed the plan" loop except for legacy VLM. max_iterations re-runs only _run_generate, not the planning phases. PipelineResult carries a single artifact set, not a candidate set.
The whole system models taste as a one-pass refinement — but the actual problem (aesthetic convergence) requires loops at the plan layer.
What this skill produces
{
"summary": {
"phases": ["route", "plan", "validate", "execute", "review", "evolve"],
"phase_can_reenter_predecessor": false,
"pipeline_result_carries_candidate_set": false,
"scoring_feeds_into_route": false,
"scoring_feeds_into_plan_in_same_run": false,
"max_iterations_scope": "execute_only",
"in_run_loops": [
{ "name": "max_iterations", "scope": "execute → review → execute", "controlled_by": "iteration count" }
],
"across_run_loops": [
{ "name": "iteration_memory feedback", "scope": "next run's prompt assembly reads prior negatives" },
{ "name": "learnings promotion", "scope": "evolve writes to learnings.json; future runs prepare-phase reads it" }
]
},
"actual_state_machine": "(mermaid or graph dsl describing today's flow)",
"desired_state_machine": "(graph showing plan↻ on critique block, candidate-set carried, scoring feedback into plan)",
"delta": [
{
"transition": "validate.blocking → plan",
"today": "blocking_findings → stop_reason; user must re-invoke orchestrate-material",
"desired": "in-run plan revision driven by blocking findings",
"minimum_change": "PipelineRunner._run_critique returns plan_revisions; runner re-enters _run_plan"
},
{
"transition": "review.iterate → plan",
"today": "iteration_memory mutated; loop exits; next run reads memory",
"desired": "in-run plan revision driven by review.before_after_diffs",
"minimum_change": "max_iterations covers plan re-entry; PipelineResult carries iteration_history"
},
{
"transition": "execute → multiple_candidates",
"today": "PipelineResult.artifacts is a single set; multi-candidate work is multiple runs",
"desired": "PipelineResult.candidates: List[CandidateResult] when an Experiment is active",
"minimum_change": "AestheticExperiment from brand-gen-experiment-modeling + List wrapper on artifacts"
}
],
"non_loops": [
"scoring → route (would let the system reroute when a scored direction underperforms; doesn't exist)",
"scoring → plan (in-run; would close the convergence loop; doesn't exist)"
],
"blast_radius": {
"introducing_plan_loop": "max_iterations semantics, PipelineResult shape, run_ledger schema",
"introducing_candidate_set": "PipelineResult.artifacts, every consumer of artifacts (UI, MCP, brand-orchestrator)"
}
}
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.
- 2mo ago First seen · 146 lines · 171 tokens per session scan A 83c2cb89e96f
brand-gen-loop-shape-assessment is a skill published in the GitHub repository velinussage/brand-gen (0 stars, last pushed 5mo ago), licensed MIT. It adds 171 tokens to every session and 1,976 once invoked, about $0.0007 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-31.
brand-gen-loop-shape-assessment compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| brand-gen-loop-shape-assessmentvelinussage/brand-gen | Skill | 0 | 5mo ago | MIT | A | 171 | Claude Code, Codex |
| systematic-debuggingopen-metadata/OpenMetadata | Skill | 16k | today | Apache-2.0 | A | 37 | Claude Code |
| log-error-digestzebbern/claude-code-guide | Skill | 4.7k | yesterday | MIT | A | 71 | Claude Code, Codex |
| cwv-optimizeradobe/skills | Skill | 321 | today | Apache-2.0 | A | 112 | Claude Code |
| ci-fixersipyourdrink-ltd/bernstein | Skill | 1.2k | today | Apache-2.0 | A | 15 | Claude Code, Codex |
| incident-response-incident-responsermyndharis/antigravity-skills | Skill | 2.0k | yesterday | MIT | A | 36 | Claude Code, Codex |
| diagnosing-missing-recordingsPostHog/posthog | Skill | 41k | today | none | A | 76 | Claude Code, Codex |