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/voxtechnologies/transmute-framework/hardennpx skills add VoxTechnologies/transmute-framework --skill hardengit clone --depth 1 https://github.com/VoxTechnologies/transmute-frameworkWrote 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/voxtechnologies/transmute-framework/harden)<a href="https://agentmods.dev/skills/voxtechnologies/transmute-framework/harden"><img src="https://agentmods.dev/badge/skills/voxtechnologies/transmute-framework/harden.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 | $0.00085 | $0.03366 |
| Opus 5 | $0.00043 | $0.01683 |
| Sonnet 5 | $0.00017 | $0.00673 |
| Haiku 4.5 | $0.00009 | $0.00337 |
Grade A, and why
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 4d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stage 6G: Error Handling, Network Failures, and Edge Cases
Read the detailed guide at ${CLAUDE_SKILL_ROOT}/references/harden-detailed-guide.md for the complete hardening procedures, teammate spawn prompts, error pattern catalogs, and report templates.
Lead a multi-agent error resilience hardening project. Systematically review the COMPLETE product for error handling gaps, network failure scenarios, race conditions, and edge cases that individual feature implementations may have missed.
Stage Sequence (recommended ordering): Stage 5B → 6A/6B/6C (parallel) → 6E (Code Refactoring) → 6F (Seed Data) → 6G (this stage) → 6D (Documentation) → 6H (Pre-Launch) → 6V → 6R → 6P/6P-R → 7 (Deploy)
Rate Limiting Scope Boundary (6A vs 6G)
Cross-stage coordination: Before implementing data-mutation rate limiting, read
./plancasting/_audits/security/report.mdfrom Stage 6A to verify which endpoints are already rate-limited (auth endpoints). Implement only DATA-MUTATION rate limiting here — auth endpoint rate limiting was handled in 6A.
Stage 6A implements rate limiting for AUTH endpoints (login, signup, password reset, forgot password / password reset initiation, MFA, session management, password change, email verification, invitation acceptance). Stage 6G (this stage) implements rate limiting for DATA-MUTATION endpoints (create, update, delete operations, file uploads, user profile updates). Verify 6A's auth-endpoint rate limiting before implementing to avoid duplication.
Prerequisites
Prerequisite: Stage 6E must have completed before 6G starts — 6G depends on refactored error handling patterns from 6E. Do NOT run 6E and 6G in parallel.
Verify before starting:
./plancasting/_audits/implementation-completeness/report.mdexists with PASS or CONDITIONAL PASS. If missing, STOP: "Stage 5B report not found — do not harden code with unverified implementation completeness."- If 5B shows FAIL, STOP. If CONDITIONAL PASS, review Category C issues and proceed with awareness.
./plancasting/_audits/refactoring/report.md(6E) exists. If missing, WARN: "Stage 6E not completed. 6G is RECOMMENDED after 6E for cleaner error handling patterns." If present, read the "Extracted Error Handling Patterns for Stage 6G" section to reuse existing patterns rather than creating duplicates.- Read
./CLAUDE.mdand./plancasting/tech-stack.mdfor project conventions. - If
./plancasting/_audits/security/report.md(6A) is available, include in teammate prompts for rate limiting scope boundaries. If missing, WARN and implement data-mutation rate limiting regardless.
What ships with it
1 file 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.
- 4d ago First seen · 175 lines · 85 tokens per session scan A 9c0a4d74d16b
harden is a skill published in the GitHub repository VoxTechnologies/transmute-framework (4 stars, last pushed 1mo ago), licensed MIT. It adds 85 tokens to every session and 3,366 once invoked, about $0.0004 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
review
Reviews code changes for concrete bugs with P0-P2 prioritized findings. Uses parallel architectural and implementation reviewers, then validates findings to remove false positives. Use when reviewing a caller-supplied diff, branch, staged changes, file set, or pull request, and use fix mode with caller-supplied…
spec
Writes high-quality product specifications through codebase research, web research, a collaborative requirements interview, and independent review, then gives the user a link to the written spec. Use when planning a feature, defining requirements, revising an existing draft, or creating a spec/PRD. Accepts…
document
Generate minimal documentation through parallel agents.
implement
Implement through pattern learning.
red-blue-review
Use when the user asks for 红蓝对抗 / 蓝军评审 / 对抗评审 / 需求评审 (adversarial review of a requirement analysis), when the user asks to 整改/按 findings 整改 (red-team revision of the analysis per review findings, §5.5), or after a complex requirement's summary.md is delivered and the human opts in - the blue army reviews red army…
requirement-alignment
Use when analyzing a requirement/PRD (分析需求/解析需求/解析PRD/分析PRD), building state machines (画状态机), sequence diagrams (时序图), decision tables (决策表) or DDL from a spec, or resuming an interrupted requirement analysis (用户说"继续") - drives the three-level intent-alignment funnel (code evidence, registered inference, structured…