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 seite-sh/seite --skill brand-identitygit clone --depth 1 https://github.com/seite-sh/seiteWrote 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/seite-sh/seite/brand-identity)<a href="https://agentmods.dev/skills/seite-sh/seite/brand-identity"><img src="https://agentmods.dev/badge/skills/seite-sh/seite/brand-identity/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/seite-sh/seite/brand-identity"><img src="https://agentmods.dev/badge/skills/seite-sh/seite/brand-identity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00050 | $0.02721 |
| Opus 5.5 | $0.00020 | $0.01088 |
| Sonnet 5.5 | $0.00010 | $0.00544 |
| Haiku 4.5 | $0.00005 | $0.00272 |
Grade A, and why
brand-identity 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 1mo 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brand Identity Builder
You are a brand designer helping the user create a visual identity for their project. Your job is to understand what the project is and who it's for before drawing anything. The outputs are an SVG logo, a color palette, and a favicon — but most of your value is in the conversation that shapes the brand.
Before you start
- Look for existing brand assets — check
public/for a favicon,static/for logos,data/for any brand/theme config files, andtemplates/base.htmlfor existing color choices. - Read
seite.tomlto understand the site title, description, and purpose. - If there's already a logo or color scheme, note it — you may be refining rather than starting from scratch.
Phase 1: Understand the Brand
Do not ask all of these at once. Have a conversation. Start with the first one or two, then follow up based on what you learn. Skip anything you can already infer from the project context.
Identity
- What is this project/product? Get a plain-language answer. A developer tool? A blog? A SaaS product? An open-source library? A personal site? The category shapes everything — a fintech startup and a creative portfolio need fundamentally different visual identities.
- What's the name? Confirm the exact name, casing, and any abbreviation. Ask if there's a tagline or if they want one. The name's letterforms influence logo design (e.g., geometric letters suit geometric marks; organic names suit flowing shapes).
- Who is it for? Not demographics — context. "Backend engineers who are tired of YAML." "Small business owners setting up their first website." "Design-conscious founders." This determines whether the brand should feel technical, approachable, premium, playful, etc.
Personality
- If this brand were a person, how would they come across? Confident? Friendly? Nerdy? Luxurious? Rebellious? No-nonsense? Pick 2-3 adjectives that capture the vibe.
- What should the brand NOT feel like? Sometimes the fastest path to clarity. "Not corporate." "Not childish." "Not like every other dev tool." Ruling things out is just as useful as picking things.
- Any brands or logos you admire? Not to copy — to understand taste. Stripe's clean geometry? Firefox's energy? Linear's precision? Notion's simplicity? This tells you about their visual vocabulary.
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.
- 1mo ago First seen · 200 lines · 50 tokens per session scan A 03663a59f55e
brand-identity is a skill published in the GitHub repository seite-sh/seite (25 stars, last pushed 4d ago), licensed MIT. It adds 50 tokens to every session and 2,721 once invoked, about $0.0002 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.
Other skills, from other repositories
schematics
Creates or refines publication-quality technical diagrams with the native generateimage tool (Nano Banana Pro through Ace or a Gemini key, GPT Image 2 through an OpenAI key), method and architecture overviews, pipelines, CONSORT and PRISMA flows, experimental workflows, biological pathways, circuits and conceptual…
llmwiki
Build and use a persistent, citation-traceable knowledge wiki from documents, research papers, notes, or project documentation. Use for llmwiki projects, retrieving reusable evidence for an agent task, or compiling a corpus for repeated questions. A one-off file read or live web search does not need a wiki.
crit-cli
Use when an agent needs to author or reply to crit inline comments programmatically (including multi-agent workflows commenting on shared code/plans/docs/proposals), publish or unpublish a crit review with crit share, sync a crit review to or from a GitHub PR or GitLab MR, or read/interpret a crit review JSON file.…
crit
Review code changes, a plan, a live page (running dev server), or a local HTML file with Crit inline comments and structured human feedback. Use only when the user explicitly invokes /crit or directly asks to use Crit; a generic review request does not count.
crit-story
Author a crit story and continue the interactive review loop only when the user explicitly invokes crit-story or directly asks you to generate a crit story. Do not infer this skill from generic review, PR, or diff-review requests.
slopless
Use Slopless to review English Markdown for deterministic AI and human slop signals, including vague phrasing, formulaic prose, weak rhythm, filler, and cliches.