What is hardening-resilience?

A read-only review of a feature's ability to handle errors, unusual inputs, translation needs, and crowded or overflowing text. It produces an audit report instead of changing application code.

Use it to inspect error handling, edge cases, translated text, input limits, and graceful behavior when parts of an application fail.

It helps reveal failures users may encounter outside the normal path, such as empty data, very long input, missing values, or network delays. It also checks whether messages can work in different languages.

hardening-resilience — Skill for Claude Code and Codex by porcupine-md

Install

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.

Any agent

npx skills add porcupine-md/jonggrang --skill hardening-resilience

Clone the repo

git clone --depth 1 https://github.com/porcupine-md/jonggrang

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/porcupine-md/jonggrang/hardening-resilience/github.svg)](https://agentmods.dev/skills/porcupine-md/jonggrang/hardening-resilience)

Your own site

<a href="https://agentmods.dev/skills/porcupine-md/jonggrang/hardening-resilience"><img src="https://agentmods.dev/badge/skills/porcupine-md/jonggrang/hardening-resilience/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/porcupine-md/jonggrang/hardening-resilience"><img src="https://agentmods.dev/badge/skills/porcupine-md/jonggrang/hardening-resilience.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 379 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00020	$0.00379
Opus 5	$0.00010	$0.00189
Sonnet 5	$0.00004	$0.00076
Haiku 4.5	$0.00002	$0.00038

Measured 12d ago against content hash 07d49e271451, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

hardening-resilience 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.

skills/library/backend/hardening-resilience/SKILL.md · 35 lines

What it actually says

Hardening & Resilience Review

Role Constraints: Reviewer (STRICTLY READ-ONLY for application code). You MAY NOT modify, fix, or write to application source code. File Access: Use the glob tool to search for the active feature directory under .jonggrang/.output/features/. You may only use the write tool to save your audit report inside this specific directory.

Objective

Evaluate the codebase for interface and backend resilience: proper error handling, i18n support, edge case management, and graceful degradation.

Execution Steps

Discover Context: Use glob and read to explore the application code modified or created for the current feature.
Review Dimensions:
- Error Handling: Are exceptions caught? Are user-friendly error messages returned? Do APIs fail gracefully?
- Edge Cases: Are empty states handled? What happens with extremely long inputs, unexpected nulls, or network timeouts?
- Internationalization (i18n): Are strings hardcoded or localized?
- Data Validation: Is boundary testing applied to inputs?
Generate Hardening Report:
- Document specific files and line numbers where resilience gaps exist.
- Detail the impact of the missing hardening measure.
- Propose exactly how the code should be fixed (do not fix it yourself).
Save Report:
- Write the findings using the write tool to .jonggrang/.output/features/<active-feature-dir>/hardening-report.md.

Completion Signal

When the hardening report is saved, output exactly:

HARDENING_REVIEW_COMPLETE

Changes

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 · 35 lines · 20 tokens per session scan A 07d49e271451

Subscribe to this mod's changes

hardening-resilience is a skill published in the GitHub repository porcupine-md/jonggrang (11 stars, last pushed 4d ago), licensed MIT. It adds 20 tokens to every session and 379 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-08-30.

Debugging Localization

js-regex-cjk-word-boundary

Fix JavaScript regex failures when matching CJK (Chinese/Japanese/Korean) text using \b word boundaries. Use when: (1) Regex pattern with \b silently fails to match Japanese, Chinese, or Korean text, (2) Pattern works for Latin/ASCII text but not CJK, (3) hasDriverLicenceCue or similar text-detection function returns…

divinevideo/divine-mobile · 177 tokens

review-all

Multi-agent code review for diffs (project-agnostic). Covers standards, bugs, security, DRY, smells, perf, tests, API contracts, a11y/i18n. Verifies each finding to eliminate false positives. Use for /review-all, pre-PR/pre-commit review, or auditing uncommitted/staged changes.

ncoevoet/claude-review-all · 74 tokens

hardening-resilience