Borrowing it
Nothing to install: this file belongs to irahardianto/awesome-agv. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/irahardianto/awesome-agv/main/.agents/skills/guardrails/SKILL.mdgit clone --depth 1 https://github.com/irahardianto/awesome-agvWrote 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/irahardianto/awesome-agv/guardrails)<a href="https://agentmods.dev/skills/irahardianto/awesome-agv/guardrails"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/guardrails/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/irahardianto/awesome-agv/guardrails"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/guardrails.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00039 | $0.00749 |
| Opus 5 | $0.00019 | $0.00375 |
| Sonnet 5 | $0.00008 | $0.00150 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
guardrails 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 11d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Guardrails Skill
Purpose
Structured checklists that ensure the agent considers all applicable rules before and after writing code. Catches issues that would otherwise only surface during verification.
When to Invoke
- Pre-Flight: At the start of Phase 2 (Implement), before writing any code
- Self-Review: At the end of Phase 2 (Implement), after writing code but before Phase 3/4
Pre-Flight Checklist
Run through this checklist before writing any code:
- Identified all applicable rules from
.agents/rules/ - Searched for existing patterns in codebase (Pattern Discovery Protocol from
architectural-pattern.md) - Confirmed project structure alignment (
project-structure.md) - Identified I/O boundaries that need abstraction
- Determined test strategy (unit/integration/E2E)
- Reviewed
rule-priority.mdfor any potential conflicts - Checked for existing structured specs (PRD/SDD/TSD/BDD/Plan) and identified applicable contracts (
CT-*) and requirements (REQ-*)
If any item cannot be checked, stop and resolve before proceeding.
Post-Implementation Self-Review
Run through this checklist after writing code, before verification:
Security
- No hardcoded secrets or configuration values
- All user input validated at system boundaries
- Parameterized queries (no string concatenation for SQL)
Testability
- All I/O operations behind interfaces/abstractions
- Business logic is pure (no side effects in calculations)
- Dependencies injected, not hardcoded
Observability
- All public operation entry points logged (start/success/failure)
- Structured logging with correlation IDs
- Appropriate log levels (not everything is INFO)
Error Handling
For universal error handling principles, see
.agents/rules/error-handling-principles.md. Below: language-specific patterns only.
- Error paths handled explicitly (no empty catch blocks)
- Errors provide context (wrapped with additional info)
- Resources cleaned up in error paths (defer/finally)
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.
- 11d ago First seen · 87 lines · 39 tokens per session scan A abab85a19aab
guardrails is a skill published in the GitHub repository irahardianto/awesome-agv (156 stars, last pushed 21d ago), licensed MIT. It adds 39 tokens to every session and 749 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-08-30.
Other skills, from other repositories
agenttrace-session-audit
Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.
maintaining-windows-health
Hands-on playbook for Windows 11 disk cleanup, dev-machine optimization, and proactive health alerting. Use when the PC is full or slow, when a BSOD / Kernel-Power 41 / crash dump / commit-memory pressure happened, when the user asks to free disk space, audit storage, set up disk/memory alerts, or restore the same…
prompt-engineering
Universal prompt engineering techniques for any LLM. Use when crafting, optimizing, or reviewing prompts for AI models. Triggers on requests like "improve this prompt", "write a system prompt", "optimize my instructions", "help me prompt engineer", "audit this prompt", "review my prompt", or when building agentic…
installing-cli-tools
Install, upgrade, configure, and verify developer CLI tools safely. Use when a user asks to install a new CLI, command-line app, SDK tool, package-manager binary, GitHub release binary, language runtime tool, or AI/vendor CLI; configure shell PATH/completions; run first login; set API keys, tokens, or env variables…
repo-activity-summary
Summarize a repository's recent engineering activity from git history — technologies, work types, churn hotspots, contributor patterns, and velocity. Use when asking "what has this repo been working on", "is this project active", "who contributes what", "where are the hotspots", or before onboarding onto an unfamiliar…
fetch-url-as-markdown
Fetch a web page (URL) and return clean Markdown via local trafilatura, with Exa MCP as a fallback for JS-rendered or anti-bot pages. Use when the user asks to read, fetch, scrape, summarize, or quote a URL — prefer this over the built-in WebFetch tool. Don't use for binary files (PDFs, images, archives) or for…