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 jaredlangleycc/nightshift-os --skill brand-guidelinesgit clone --depth 1 https://github.com/jaredlangleycc/nightshift-osWrote 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/jaredlangleycc/nightshift-os/brand-guidelines)<a href="https://agentmods.dev/skills/jaredlangleycc/nightshift-os/brand-guidelines"><img src="https://agentmods.dev/badge/skills/jaredlangleycc/nightshift-os/brand-guidelines.svg" alt="Measured on agentmods" 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.00147 | $0.04422 |
| Opus 5 | $0.00073 | $0.02211 |
| Sonnet 5 | $0.00029 | $0.00884 |
| Haiku 4.5 | $0.00015 | $0.00442 |
Grade A, and why
brand-guidelines 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 7d 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 — 438 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brand Guidelines
The documentation skill. Turns the brand-strategist brief into a working reference document that the user, contractors, designers, and future-self can use to keep the brand coherent. Stage-aware. Pre-Rev gets a 1-page sketch so they don't burn 3 weeks before a customer exists. Scaling Solo gets full guidelines because incoherence costs real money at that stage.
When this skill triggers
- "Document my brand"
- "Build brand guidelines"
- "Brand standards"
- "Brand style guide"
- "Brand book"
- "Visual brand doc"
- "Design system"
- "Where do I write my brand down"
- Auto-activated after
brand-strategistfinishes and the user has a locked brief - Auto-activated when the user briefs a new contractor or designer
NOT for: brand identity work from scratch (use brand-strategist), voice enforcement on every draft (use voice-rules), logo design execution (refer out to a designer with this doc as the brief).
What guidelines do
Guidelines are operational. They turn brand decisions into:
- Decisions a designer can execute without asking 12 questions
- A do/don't grid the user can reference at 11pm when shipping a post
- A version-controlled snapshot of "what the brand looks like as of [date]"
- A briefing document for any contractor (VA, designer, developer, social manager)
Guidelines are NOT:
- A 40-page brand book that nobody reads
- A vanity document that signals "real business" without doing operational work
- A static artifact that never updates
- An excuse to delay shipping
The guidelines build process (7 sections)
Work through each section in order. Show progress as you go. Lock each section before moving on. Pre-Rev users get truncated versions (noted inline). Stable Solo and Scaling Solo get full builds.
Section 1: Brand identity snapshot
Top of the guidelines. The "what is this brand" answer in 30 seconds of reading.
Pull from the brand-strategist brief if available. If not, run a 3-question intake:
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 438 lines · 147 tokens per session scan A a76ece0e8a7e
brand-guidelines is a skill published in the GitHub repository jaredlangleycc/nightshift-os (3 stars, last pushed 1mo ago), licensed MIT. It adds 147 tokens to every session and 4,422 once invoked, about $0.0007 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.
Other skills, from other repositories
Brand Guidelines Generator
Create and maintain brand style guides for consistent visual identity.
html-ppt-zhangzara-studio
A photography studio's portfolio-and-rate deck — the signature work, the process, and the packages that win the brief. Built as a decision-grade design craft deck for prospective clients.
top-design
Create award-winning, immersive web experiences at the level of Awwwards-featured agencies. Use when the user mentions "Awwwards quality", "make my site stunning", "scroll animations", "parallax storytelling", "cinematic web design", "portfolio site", or "brand experience". Also trigger when elevating a standard…
design-everyday-things
Apply foundational design principles: affordances, signifiers, constraints, feedback, and conceptual models. Use when the user mentions "why is this confusing", "affordance", "error prevention", "discoverability", "human-centered design", "mental model", "mapping", "seven stages of action", "users keep making…
sxo
Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…
screenshot-optimization
When the user wants to design, optimize, or evaluate App Store screenshots and preview videos. Also use when the user mentions "screenshots", "app preview", "product page design", "screenshot design", "creative assets", or "what should my screenshots show". For A/B testing screenshots, see ab-test-store-listing. For…