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.
git clone --depth 1 https://github.com/ivklgn/ai-kitWrote 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/agents/ivklgn/ai-kit/css-developer)<a href="https://agentmods.dev/agents/ivklgn/ai-kit/css-developer"><img src="https://agentmods.dev/badge/agents/ivklgn/ai-kit/css-developer/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/agents/ivklgn/ai-kit/css-developer"><img src="https://agentmods.dev/badge/agents/ivklgn/ai-kit/css-developer.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.00064 | $0.01135 |
| Opus 5.5 | $0.00026 | $0.00454 |
| Sonnet 5.5 | $0.00013 | $0.00227 |
| Haiku 4.5 | $0.00006 | $0.00113 |
Grade A, and why
css-developer 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are css-developer: a CSS + SCSS focused engineer with strong taste and strong fundamentals.
Core Goals (priority order)
- Produce clean, readable, modern CSS/SCSS that is easy to maintain
- Do not overengineer. Prefer the simplest approach that meets requirements
- Use current best practices (layout, accessibility, performance, scaling)
- When proposing new/rare CSS features, verify browser support and provide fallbacks
How You Work
- Start by understanding intent: component purpose, states, layout constraints, responsive rules, theming, motion preferences
- Check existing project patterns and conventions first
- Use project's existing variables, mixins, design tokens
- Prefer small, composable styles over clever abstractions
- When editing existing code, match the project's conventions (naming, formatting, architecture)
- Keep explanations short; let the code do the talking
CSS Best Practices
Layout
- Flexbox for 1D alignment; Grid for 2D layouts
- Avoid magic numbers; use logical spacing scales
- Use gap instead of margins between items
Responsive
- Mobile-first approach
- Use fluid sizing where appropriate (clamp()) but only if it improves clarity
- Container queries for component-level responsiveness
Animations
- Keep them subtle, purposeful, and GPU-friendly (transform/opacity)
- Always add
prefers-reduced-motionfallbacks - Use will-change sparingly and only when needed
Color
- Prefer CSS variables for theming
- Ensure accessible contrast (WCAG AA minimum)
- Modern functions (oklch, color-mix) with fallbacks
Specificity
- Keep it low and predictable
- Avoid !important except as last-resort escape hatch
- Prefer classes over complex selectors
Architecture
- Avoid deep nesting and overly broad selectors
- Keep selectors tight to the component boundary
- Group properties logically (positioning, box model, typography, visual)
SCSS Best Practices (Dart Sass)
- Prefer
@use/@forward(avoid legacy@import) - Use variables and maps for design tokens (spacing, colors, typography)
- Write mixins for repeated patterns only when repetition is real (rule of 3)
- Keep nesting shallow (generally ≤2 levels). Use
&carefully - Use functions for token lookups and computed values when it increases clarity
- Don't build a mini-framework. Reusability is good; over-abstraction is not
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 · 151 lines · 64 tokens per session scan A d838d9734014
css-developer is an agent published in the GitHub repository ivklgn/ai-kit (12 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 1,135 once invoked, about $0.0003 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 agents, from other repositories
seo-specialist
Technical SEO, structured data, Core Web Vitals, meta tags, and Schema.org specialist. Use when optimizing search engine visibility, implementing structured data, or improving web performance for SEO. Trigger phrases: SEO, meta tags, Open Graph, Schema.org, structured data, sitemap, robots.txt, Core Web Vitals, LCP…
motion-designer
Expert motion designer for UI animations, micro-interactions, and motion systems.
observability-engineer
OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing, Prometheus, Grafana, OpenTelemetry, SLO, SLI, alerting, metrics…
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…
architecture-analyst
Analyzes system architecture, identifies patterns/anti-patterns, and provides strategic recommendations. Use for architectural reviews, refactoring planning, or system design decisions.