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 ai-analyst-lab/ai-analyst --skill guardrailsgit clone --depth 1 https://github.com/ai-analyst-lab/ai-analystWrote 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/ai-analyst-lab/ai-analyst/guardrails)<a href="https://agentmods.dev/skills/ai-analyst-lab/ai-analyst/guardrails"><img src="https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst/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/ai-analyst-lab/ai-analyst/guardrails"><img src="https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst/guardrails.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.00228 | $0.02272 |
| Opus 5 | $0.00114 | $0.01136 |
| Sonnet 5 | $0.00046 | $0.00454 |
| Haiku 4.5 | $0.00023 | $0.00227 |
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 2d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Guardrails Awareness
Purpose
Ensure that every success metric is paired with at least one guardrail metric, and that positive findings are checked for trade-offs before being presented as wins.
When to Use
Apply this skill in two situations:
- When defining metrics — after using the Metric Spec skill, check whether the metric has a guardrail pair
- When reporting positive findings — before presenting any improvement, check whether a related guardrail metric degraded
Instructions
What Are Guardrails?
A guardrail metric is a metric you don't want to degrade while optimizing a success metric. Guardrails protect against winning the metric game while losing the business game.
SUCCESS METRIC: The metric you're trying to improve
GUARDRAIL: The metric that must not get worse
The rule: Never celebrate an improvement on a success metric without checking its guardrail(s). An improvement with a degraded guardrail is a trade-off, not a win.
Common Guardrail Pairs
| Success Metric | Guardrail(s) | Why |
|---|---|---|
| Conversion rate | Average order value, Return rate | Aggressive discounts inflate conversion but erode margin and invite returns |
| Signup rate | Activation rate, 7-day retention | Lowering the signup bar brings in unqualified users who churn immediately |
| Revenue per user | User satisfaction (NPS/CSAT), Support ticket volume | Monetization pressure degrades experience |
| Feature adoption | Core workflow completion, Session duration | Forcing feature usage may disrupt existing workflows |
| Time to complete (speed) | Error rate, Quality score | Rushing degrades accuracy |
| Cost reduction | Quality, Customer satisfaction | Cutting costs can degrade service |
| Engagement (DAU, sessions) | Revenue per user, Churn rate | Engagement tricks (notifications, dark patterns) don't translate to value |
| Support resolution time | Customer satisfaction, Reopen rate | Fast close ≠ good close if tickets reopen |
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.
- 2d ago First seen · 174 lines · 228 tokens per session scan A 90cb098e0eee
guardrails is a skill published in the GitHub repository ai-analyst-lab/ai-analyst (298 stars, last pushed 3d ago), licensed MIT. It adds 228 tokens to every session and 2,272 once invoked, about $0.0011 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-12.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…