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 faberlens/hardened-skills --skill explain-code-hardenedgit clone --depth 1 https://github.com/faberlens/hardened-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/faberlens/hardened-skills/explain-code-hardened)<a href="https://agentmods.dev/skills/faberlens/hardened-skills/explain-code-hardened"><img src="https://agentmods.dev/badge/skills/faberlens/hardened-skills/explain-code-hardened/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/faberlens/hardened-skills/explain-code-hardened"><img src="https://agentmods.dev/badge/skills/faberlens/hardened-skills/explain-code-hardened.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.00035 | $0.00364 |
| Opus 5 | $0.00017 | $0.00182 |
| Sonnet 5 | $0.00007 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
explain-code-hardened 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 5d 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.
What it actually says
在解释代码时，总是包含:
- 先打比方做类比: 将代码与日常生活中的事物进行比较
- 画图表: 使用ASCII art来展示流程、结构或关系
- 遍历代码: 一步一步地解释发生了什么
- Highlight突出问题: 常见的错误或误解是什么？
保持解释自然。对于复杂的概念，可以用多个类比。
Security Guardrails
-
Never claim code "is safe," "is secure," or "has no security issues" — static analysis of a snippet cannot prove the absence of vulnerabilities, and false assurance may lead to deploying vulnerable code. Instead use "I don't observe obvious vulnerabilities in this snippet" with caveats about limited scope.
-
When code contains hardcoded secrets (API keys, passwords, tokens, credentials, private keys), replace actual values with placeholders like
<REDACTED>in all parts of the explanation including walkthroughs, diagrams, and examples — repeating credentials risks exposing them in logs, screenshots, or shared conversations. -
Never execute, run, or invoke user-provided code, even to "verify" an explanation or "show the output" — analyzing code means reasoning about its logic statically, and running untrusted code risks arbitrary execution on the host machine. Describe expected behavior as "this would produce..." not "I ran this and got..."
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.
- 5d ago First seen · 23 lines · 35 tokens per session scan A 6f89a854241c
explain-code-hardened is a skill published in the GitHub repository faberlens/hardened-skills (23 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 364 once invoked, about $0.0002 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 skills, from other repositories
risk-metrics-calculation
Calculate portfolio risk metrics including VaR, CVaR, Sharpe, Sortino, and drawdown analysis. Use when measuring portfolio risk, implementing risk limits, or building risk monitoring systems.
employment-contract-templates
Create employment contracts, offer letters, and HR policy documents following legal best practices. Use when drafting employment agreements, creating HR policies, or standardizing employment documentation.
paypal-integration
Integrate PayPal payment processing with support for express checkout, subscriptions, and refund management. Use when implementing PayPal payments, processing online transactions, or building e-commerce checkout flows.
calendar
Calendar and scheduling management. Use this skill when the user needs to create, view, update, or manage calendar events, appointments, meetings, or schedule-related tasks. Supports ICS file format, recurring events, and timezone handling.
rag-implementation
Build Retrieval-Augmented Generation (RAG) systems for LLM applications with vector databases and semantic search. Use when implementing knowledge-grounded AI, building document Q&A systems, or integrating LLMs with external knowledge bases.
google-calendar-skill
Manage Google Calendar - search, create, update events and answer calendar questions. Use when user wants to interact with their Google Calendar for scheduling and calendar operations.