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 gc-victor/supersimple --skill securitygit clone --depth 1 https://github.com/gc-victor/supersimpleWrote 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/gc-victor/supersimple/security)<a href="https://agentmods.dev/skills/gc-victor/supersimple/security"><img src="https://agentmods.dev/badge/skills/gc-victor/supersimple/security.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.1 | $0.00045 | $0.00563 |
| Opus 5 | $0.00023 | $0.00282 |
| Sonnet 5 | $0.00009 | $0.00113 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
security 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security and Hardening
Treat every external input as hostile, every secret as sacred, and every authorization check as mandatory. This skill MUST apply security constraints to every line of code that touches user data, authentication, or external systems.
What to Do
- Validate all external input at system boundaries.
- Parameterize all database queries.
- Encode output to prevent XSS; use framework auto-escaping.
- Hash passwords with bcrypt/scrypt/argon2 (salt rounds ≥ 12).
- Use httpOnly, secure, sameSite cookies for sessions.
- Check authorization on every protected endpoint.
- Set security headers (CSP, HSTS, X-Frame-Options, X-Content-Type-Options).
- Use HTTPS for all external communication.
- Run dependency audits before release.
- Restrict CORS to known origins.
- Sanitize file uploads by type and size; do not trust extensions.
Ask First
- Adding or changing authentication flows.
- Storing new categories of sensitive data.
- Adding external service integrations.
- Changing CORS configuration.
- Adding file upload handlers.
- Modifying rate limiting.
- Granting elevated permissions.
Never Do
- Commit secrets to version control.
- Log sensitive data.
- Trust client-side validation as a security boundary.
- Disable security headers for convenience.
- Use
eval()orinnerHTMLwith user-provided data. - Store sessions in client-accessible storage.
- Expose stack traces or internal errors to users.
Process
- Identify the attack surface (input points, auth, data flow).
- Verify input validation exists at boundaries.
- Check authorization on every affected endpoint.
- Confirm secrets are not hardcoded or logged.
- Verify security headers and transport security.
- Run
npm audit(or equivalent) and triage findings.
Verification
- No critical or high vulnerabilities in dependencies.
- No secrets in source code or git history.
- All user input validated at system boundaries.
- Authentication and authorization checked on every protected endpoint.
- Security headers present in responses.
- Error responses do not expose internal details.
- Rate limiting active on authentication endpoints.
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 · 72 lines · 45 tokens per session scan A cb39ff0f10f1
security is a skill published in the GitHub repository gc-victor/supersimple (33 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 563 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
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…