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 Yashraj00700/indian-gov-ui-skills --skill indian-gov-web-uigit clone --depth 1 https://github.com/Yashraj00700/indian-gov-ui-skillsWrote 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/yashraj00700/indian-gov-ui-skills/indian-gov-web-ui)<a href="https://agentmods.dev/skills/yashraj00700/indian-gov-ui-skills/indian-gov-web-ui"><img src="https://agentmods.dev/badge/skills/yashraj00700/indian-gov-ui-skills/indian-gov-web-ui/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/yashraj00700/indian-gov-ui-skills/indian-gov-web-ui"><img src="https://agentmods.dev/badge/skills/yashraj00700/indian-gov-ui-skills/indian-gov-web-ui.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.00095 | $0.04556 |
| Opus 5 | $0.00048 | $0.02278 |
| Sonnet 5 | $0.00019 | $0.00911 |
| Haiku 4.5 | $0.00010 | $0.00456 |
Grade A, and why
indian-gov-web-ui 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 12d 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Indian Government Web UI
Overview
Indian government web UI is governed by three documents that do different jobs:
| Document | What it governs | Binding? |
|---|---|---|
| GIGW 3.0 | Required content and behaviour — what must be on a page | Mandatory for Central + State government sites at any level. ⚠️ Intranet applications are "recommended", not mandated (see gigw-requirements.md Scope) — but that is not a WCAG exemption |
| DBIM v3.0 | Visual identity — palette, type scale, header/footer/homepage anatomy | Written for Government of India platforms. Voluntary for a state government or state corporation |
| UX4G | Component library — v2 is a Bootstrap 5 fork, v3 is a rewrite | Advisory only. Binds solely when written into a procurement SoW/TOR. No official React package exists |
Core principle: GIGW tells you what must exist, DBIM tells you what it should look like, UX4G gives you components. Only WCAG will get you fined.
Which WCAG version are you actually building to?
Four different standards get cited in this space. Resolve it explicitly at project start:
| Source | Says |
|---|---|
| GIGW 3.0 §5.2 | WCAG 2.1 Level AA |
| Pragya Prasun direction (ix) | WCAG 2.0 Level AA |
| SC 2.5.7 (dragging) | WCAG 2.2 — not in force in India |
| Draft RPwD Rules 2026 | IS 17802 Parts 1 & 2 |
Recommended default: build to WCAG 2.1 AA. It is what GIGW 3.0 adopts, it is a strict superset of the 2.0 AA the court direction cites, and it is what IS 17802 is aligned to. Treat 2.2-only criteria (like 2.5.7) as good practice you should still follow, not as current legal exposure.
⚠️ The line-height trap — DBIM contradicts WCAG
- DBIM §4 prescribes line height 1.2–1.5 × type size.
- WCAG 1.4.12 (which GIGW adopts) requires text to remain readable at line height ≥ 1.5 ×.
- Devanagari needs ≥ 1.7 — matras and conjuncts collide below that.
Implementing DBIM's 1.2 floor literally ships a WCAG violation. Use 1.5 minimum for Latin body text and 1.7+ for Devanagari. DBIM's lower bound is for display headings only.
What ships with it
3 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.
- 12d ago First seen · 282 lines · 95 tokens per session scan A 8bc2286aedfc
indian-gov-web-ui is a skill published in the GitHub repository Yashraj00700/indian-gov-ui-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 95 tokens to every session and 4,556 once invoked, about $0.0005 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-visual-language
A brand's visual tone — playful or serious, rounded or angular — should be consistent across all UI elements. Shape language in typography, border-radius, and iconography communicates personality before a single word is read. Use when establishing a design system, choosing icon libraries, setting border-radius tokens…
micro-interactions
Micro-interactions are small, purposeful animations and responses that reward the user and make the interface feel alive — an animated icon, a satisfying toggle, a subtle reveal. Borrowed from the natural world, they add delight without distraction. Use when designing interactive components, success states, toggles…
elevation-and-depth
Elevation — subtle shadows and layering — communicates visual hierarchy by lifting elements above the surface. Combined with border-radius, it creates the tactile quality of cards, modals, and interactive surfaces. Use when designing cards, dropdowns, modals, tooltips, or any floating UI element.
loading-states-and-perceived-performance
Manage user expectations during wait times with appropriate loading states — from simple spinners to complex skeleton screens and staggered animations. Perceived performance is often more important than actual load time. Use when designing data-heavy components, handling API calls, building hero sections, or improving…
motion-and-storytelling
Disney's 12 animation principles, cinematic storytelling techniques, and comic book conventions apply to web UI — used subtly, they make interfaces feel alive, intentional, and emotionally resonant. Use when designing transitions, micro-interactions, onboarding flows, scroll animations, or any motion in the UI.
responsive-paradigms
Mobile, tablet, and desktop are different interaction paradigms — not the same layout scaled up or down. Sections can be hidden, repositioned, or made sticky on mobile. Navigation and primary actions move. Use when designing responsive layouts, adapting desktop UI for mobile, or deciding what to show on each…