Borrowing it
Nothing to install: this file belongs to oaslananka/ssh-mcp-pro. 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/oaslananka/ssh-mcp-pro/main/.opencode/skills/security-guardrails/SKILL.mdgit clone --depth 1 https://github.com/oaslananka/ssh-mcp-proWrote 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/oaslananka/ssh-mcp-pro/security-guardrails)<a href="https://agentmods.dev/skills/oaslananka/ssh-mcp-pro/security-guardrails"><img src="https://agentmods.dev/badge/skills/oaslananka/ssh-mcp-pro/security-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/oaslananka/ssh-mcp-pro/security-guardrails"><img src="https://agentmods.dev/badge/skills/oaslananka/ssh-mcp-pro/security-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.00030 | $0.00149 |
| Opus 5 | $0.00015 | $0.00075 |
| Sonnet 5 | $0.00006 | $0.00030 |
| Haiku 4.5 | $0.00003 | $0.00015 |
Grade A, and why
security-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 8d 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
Security Guardrails Skill
Use this skill whenever an SSH task could affect confidentiality, integrity, availability, credentials, or production state.
Rules
- Confirm the target host and environment.
- Separate diagnostics from mutation.
- Redact secrets and private data.
- Avoid broad scripts when a narrow command is enough.
- Require explicit approval for privileged, destructive, or service-affecting work.
- Include rollback or recovery notes for every approved change.
Response requirements
Return risk level, approval requirement, evidence, exact plan, rollback path, and unresolved risk.
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.
- 8d ago First seen · 22 lines · 30 tokens per session scan A fb389775d844
security-guardrails is a skill published in the GitHub repository oaslananka/ssh-mcp-pro (2 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 149 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-31.
Other skills, from other repositories
scaled-swarm-predict
Large-scale social simulation with 50-200 demographically diverse AI personas debating on a simulated Twitter/Reddit board to predict outcomes.
swarm-predict
Multi-perspective risk analysis using structured persona debate before deploying changes.
spec-driven-development
Build software via spec-driven development (github/spec-kit). Whenever the user asks for a feature larger than a one-line tweak, scaffold a spec-kit project, capture WHAT + WHY, declare tech stack, break into tasks, then iterate the implementation until tests pass.
morning-briefing
Generate a concise daily infrastructure briefing. Covers: service health, resource usage, security events, overnight incidents, and cost tracking. Designed for Telegram/chat delivery.
security-hardening
Continuous security posture assessment. Scores the system, auto-fixes safe issues, proposes fixes for risky ones. Every change audited.
self-healing
Detect service failures and system anomalies. Diagnose root causes. Auto-remediate using NixOS rollback, service restart, or config repair. Every action logged to the hash-chained audit ledger.