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 avmnu-sng/sutra --skill security-hygienegit clone --depth 1 https://github.com/avmnu-sng/sutraWrote 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/avmnu-sng/sutra/security-hygiene)<a href="https://agentmods.dev/skills/avmnu-sng/sutra/security-hygiene"><img src="https://agentmods.dev/badge/skills/avmnu-sng/sutra/security-hygiene/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/avmnu-sng/sutra/security-hygiene"><img src="https://agentmods.dev/badge/skills/avmnu-sng/sutra/security-hygiene.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.00046 | $0.01753 |
| Opus 5 | $0.00023 | $0.00877 |
| Sonnet 5 | $0.00009 | $0.00351 |
| Haiku 4.5 | $0.00005 | $0.00175 |
Grade A, and why
security-hygiene 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 9d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security hygiene
Run /security-review first for what it owns: it reads the working diff for
injected vulnerabilities -- SQL injection, unsafe deserialization, path
traversal, secrets committed in this change. That is diff-level review of code
you wrote.
This skill covers the angles it does not: the standing liabilities you take on around the code -- dependencies, lockfiles, credentials, advisories, and the supply chain that delivers all of them. A clean diff can still pull in a compromised package, widen a token's scope, or ignore a live advisory. Those never show up in a diff scan.
Security work sits at the T3 verification floor (see /sutra:effort-calibration):
stakes force the full floor no matter how small the change looks. Adding one
line to a manifest is a one-line diff and a T3 decision. Do not let diff size
talk you out of the floor.
1. Vet a dependency BEFORE you add it
A dependency is a standing liability, not a free function. You inherit its code, its transitive tree, its maintainers, and its future bugs. Vet before adding -- removal after the fact is far more expensive.
Check four things and record the answers:
- Transitive blast radius. What else does it pull in? Resolve the full transitive tree, not just the direct package. A three-line helper that drags in forty transitive packages is forty liabilities, not one. Prefer a smaller tree; prefer writing the three lines yourself when the tree is absurd.
- Maintenance health. When was the last release? Are there open critical issues with no maintainer response? What is the bus factor -- one unpaid maintainer, or a funded team? A package last released four years ago with open CVEs is abandonware.
- License compatibility. Confirm the license is compatible with your project's distribution terms. A copyleft dependency in a permissively licensed product is a legal defect, not a nit. Check the transitive tree's licenses too, not just the direct one.
- Known advisories. Query the advisory database for the exact version you intend to pin. A package with an unpatched high-severity advisory does not enter the tree until the advisory is resolved or you have a recorded mitigation.
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.
- 9d ago First seen · 148 lines · 46 tokens per session scan A 526753cee7a0
security-hygiene is a skill published in the GitHub repository avmnu-sng/sutra (2 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 1,753 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
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
memstack-deployment-domain-ssl
Use this skill when the user says 'setup domain', 'configure DNS', 'SSL certificate', 'domain-ssl', 'custom domain', 'HTTPS setup', or needs to configure DNS records, SSL certificates, and custom domains for any hosting provider. Do NOT use for full deployment workflows.
memstack-development-refactor-planner
Use this skill when the user says 'refactor', 'refactoring plan', 'code cleanup', 'reduce duplication', 'simplify code', 'tech debt', 'god class', 'tight coupling', or needs to systematically improve existing code. Identifies targets, assesses risk, and builds incremental execution plans. Do NOT use for writing new…
memstack-product-feedback-analyzer
Use this skill when the user says 'analyze feedback', 'feedback analysis', 'what are customers asking for', or has support tickets, reviews, or survey data to categorize, score, and prioritize into actionable reports. Do NOT use for competitor analysis or market research.
memstack-seo-meta-tag-optimizer
Use this skill when the user says 'meta tags', 'title tag', 'meta description', 'optimize meta', 'SERP preview', or needs to write or optimize HTML meta tags for better search visibility and click-through rates. Do NOT use for schema markup or full site audits.
familiar
Use when the user says 'dispatch', 'send familiar', 'split task', or needs work split across parallel CC sessions.