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 agentmods add skills/urmzd/dotfiles/style-brandnpx skills add urmzd/dotfiles --skill style-brandgit clone --depth 1 https://github.com/urmzd/dotfilesWrote 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/urmzd/dotfiles/style-brand)<a href="https://agentmods.dev/skills/urmzd/dotfiles/style-brand"><img src="https://agentmods.dev/badge/skills/urmzd/dotfiles/style-brand.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.00055 | $0.00763 |
| Opus 5 | $0.00028 | $0.00381 |
| Sonnet 5 | $0.00011 | $0.00153 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
style-brand 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 6d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visual Identity
Theme & Font
| Element | Choice |
|---|---|
| Theme | (example: Cyberdream, 256-color) |
| Font | (example: MonaspiceNe Nerd Font, 16pt) |
Example palette (Cyberdream -- substitute your own):
| Color | Hex |
|---|---|
| Background | #16181a |
| Foreground | #ffffff |
| Red | #ff6e5e |
| Green | #5eff6c |
| Yellow | #f1ff5e |
| Blue | #5ea1ff |
| Magenta | #bd5eff |
| Cyan | #5ef1ff |
| Selection | #3c4048 |
teasr Demo Template
Terminal demos are recorded with a consistent template using whatever recorder you prefer (this portfolio uses teasr):
[output]
dir = "./showcase"
formats = [{ output_type = "gif" }, { output_type = "png" }]
[[scenes]]
type = "terminal"
name = "demo"
theme = "dracula"
cols = 100
rows = 24
frame_duration = 80
[[scenes.interactions]]
type = "type"
text = "export PS1='> '"
hidden = true
[[scenes.interactions]]
type = "key"
key = "enter"
hidden = true
[[scenes.interactions]]
type = "wait"
duration = 500
hidden = true
# Demo commands go here
[[scenes.interactions]]
type = "type"
text = "<command>"
speed = 50
[[scenes.interactions]]
type = "key"
key = "enter"
[[scenes.interactions]]
type = "wait"
duration = 2000
teasr Demo Capture
teasr automates demo capture with teasr.toml config:
- Scene types: web (Chrome DevTools), terminal (PTY→SVG→PNG), screen (xcap)
- Output formats: png, gif
- Standard output dir:
showcase/(default:./teasr-output) - Naming:
demo.png,demo.gif,demo-<feature>.png - CI integration: invoke your recorder via a reusable action (this portfolio uses
urmzd/teasr/.github/actions/teasr@main)
Asset Directory Convention
showcase/ directory: demo.png or demo.gif (hero, 80% width), demo-<feature>.png (feature captures), example_results/ (gallery, 30% width each).
Demo Priority
teasr (automated) > manual screenshots
Branding Consistency
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.
- 6d ago First seen · 109 lines · 55 tokens per session scan A 86e08badacb0
style-brand is a skill published in the GitHub repository urmzd/dotfiles (3 stars, last pushed 24d ago), licensed Apache-2.0. It adds 55 tokens to every session and 763 once invoked, about $0.0003 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
scientific-schematics
Create publication-quality scientific diagrams using Nano Banana 2 AI with smart iterative refinement. Uses Gemini 3.1 Pro Preview for quality review. Only regenerates if quality is below threshold for your document type. Specialized in neural network architectures, system diagrams, flowcharts, biological pathways…
infographics
Create professional infographics using Nano Banana Pro AI with smart iterative refinement. Uses Gemini 3 Pro for quality review. Integrates research-lookup and web search for accurate data. Supports 10 infographic types, 8 industry styles, and colorblind-safe palettes.
scientific-visualization
Meta-skill for publication-ready figures. Use when creating journal submission figures requiring multi-panel layouts, significance annotations, error bars, colorblind-safe palettes, and specific journal formatting (Nature, Science, Cell). Orchestrates matplotlib/seaborn/plotly with publication styles. For quick…
astropy
Core Python library for astronomy and astrophysics workflows that need Astropy APIs, including units/quantities, coordinates, FITS I/O, tables, time systems, WCS, and cosmology. Use when implementing or debugging astronomical data analysis code with Astropy.
benchling-integration
Benchling Python SDK and REST API integration for registry entities, inventory, ELN entries, workflows, Benchling Apps, and Data Warehouse queries. Use when automating lab data with benchling-sdk or the v2 API.
ralph-loop
Ralph Wiggum 迭代开发循环。三阶段工作流(需求→规划→构建),每阶段有 code review + 测试 gate。 触发词:ralph loop、迭代开发、interview me、plan system、build system。.