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/terrene-foundation/kailash-coc-claude-pyWrote 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/commands/terrene-foundation/kailash-coc-claude-py/i-harden)<a href="https://agentmods.dev/commands/terrene-foundation/kailash-coc-claude-py/i-harden"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/i-harden/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/commands/terrene-foundation/kailash-coc-claude-py/i-harden"><img src="https://agentmods.dev/badge/commands/terrene-foundation/kailash-coc-claude-py/i-harden.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.00017 | $0.00786 |
| Opus 5 | $0.00009 | $0.00393 |
| Sonnet 5 | $0.00003 | $0.00157 |
| Haiku 4.5 | $0.00002 | $0.00079 |
Grade A, and why
i-harden 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 8d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- i-harden — 88% identical, 5 lines differ
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/i-harden - Production Hardening for Frontend
Purpose
Prepare frontend interfaces for real-world usage by stress-testing against imperfect conditions: long text, missing data, slow networks, diverse languages, and unconventional inputs.
Adapted from Impeccable (Apache 2.0), enhanced for enterprise contexts.
Usage
| Command | Action |
|---|---|
/i-harden |
Full production hardening audit of current file/component |
/i-harden $ARGUMENTS |
Focused hardening on a specific area (e.g., text, i18n, errors, edge-cases) |
Philosophy
"Designs that only work with perfect data aren't production-ready."
Enterprise users have long names, mixed-language content, slow connections, and unexpected input. Hardened interfaces handle all of it gracefully.
Workflow
Step 1: Load Hardening Checklist
Read skills/23-uiux-design-principles/production-hardening.md for the full 6-category checklist covering:
- Text & Content Resilience -- overflow, length extremes, dynamic content
- Internationalization -- text expansion, formatting, character encoding
- Error States & Recovery -- network errors, HTTP status handling, form errors
- Edge Cases & Boundary -- empty states, loading states, data volume, concurrency
- Accessibility Resilience -- zoom, keyboard nav, screen reader, touch targets
- Performance Under Stress -- lazy loading, virtual scrolling, debouncing
If $ARGUMENTS specifies a focus area, evaluate only that category. Otherwise, evaluate all six.
Step 2: Evaluate Current Code
For each category in scope:
- Read the target component/page files
- Check each item against the detailed checklist
- Note PASS, FAIL, or N/A for each item
- For FAILs, draft a concrete fix with code direction
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.
- 8d ago First seen · 99 lines · 17 tokens per session scan A d3692aac26d7
i-harden is a command published in the GitHub repository terrene-foundation/kailash-coc-claude-py (12 stars, last pushed 23d ago), licensed Apache-2.0. It adds 17 tokens to every session and 786 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
test-bar
Generate a floating QA test overlay for the current branch's UI changes. Use when user says /test-bar, needs visual QA scenarios, or wants to test conditional rendering paths.
build-from-figma
You are the master orchestrator for converting a Figma design into a fully working, tested React application. You receive a Figma URL and guide the entire process through 9 phases, using specialized skills and agents.
wp-responsive-check
Responsive validation — screenshots at 5 viewports, checks for layout issues.
stark-qa
Use this command to require proof before calling a UI "good.".
sdcorejs-angular-smoke-tests
Use these prompts in VS Code Chat with SDCoreJS mode.
test
Generate Vitest tests for Vue components or functions.