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 shwilliamson/automatasaurus --skill security-standardsgit clone --depth 1 https://github.com/shwilliamson/automatasaurusWrote 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/shwilliamson/automatasaurus/security-standards)<a href="https://agentmods.dev/skills/shwilliamson/automatasaurus/security-standards"><img src="https://agentmods.dev/badge/skills/shwilliamson/automatasaurus/security-standards/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/shwilliamson/automatasaurus/security-standards"><img src="https://agentmods.dev/badge/skills/shwilliamson/automatasaurus/security-standards.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.00028 | $0.01883 |
| Opus 5.5 | $0.00011 | $0.00753 |
| Sonnet 5.5 | $0.00006 | $0.00377 |
| Haiku 4.5 | $0.00003 | $0.00188 |
Grade A, and why
security-standards 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 2mo 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 — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Standards
Guidelines for writing secure code and avoiding common vulnerabilities.
Core Principles
- Never trust user input - Validate and sanitize everything
- Least privilege - Grant minimum necessary permissions
- Defense in depth - Multiple layers of protection
- Fail securely - Errors should not expose sensitive data
- Keep secrets secret - Never commit credentials
Input Validation
Validate All Input
// Bad: Trust user input
const userId = req.params.id;
const user = await db.query(`SELECT * FROM users WHERE id = ${userId}`);
// Good: Validate and parameterize
const userId = parseInt(req.params.id, 10);
if (isNaN(userId) || userId < 0) {
throw new ValidationError('Invalid user ID');
}
const user = await db.query('SELECT * FROM users WHERE id = $1', [userId]);
Allowlist Over Denylist
// Bad: Trying to block bad input
const sanitized = input.replace(/<script>/gi, '');
// Good: Only allow expected patterns
const ALLOWED_PATTERN = /^[a-zA-Z0-9_-]+$/;
if (!ALLOWED_PATTERN.test(input)) {
throw new ValidationError('Invalid characters');
}
Type Coercion
// Bad: Loose comparison allows bypass
if (req.body.admin == true) { ... }
// Good: Strict type checking
if (req.body.admin === true && typeof req.body.admin === 'boolean') { ... }
SQL Injection Prevention
Always Use Parameterized Queries
// Bad: String concatenation
db.query(`SELECT * FROM users WHERE email = '${email}'`);
// Good: Parameterized query
db.query('SELECT * FROM users WHERE email = $1', [email]);
// Good: ORM with proper escaping
User.findOne({ where: { email } });
XSS Prevention
Escape Output
// Bad: Direct HTML insertion
element.innerHTML = userComment;
// Good: Text content (auto-escapes)
element.textContent = userComment;
// Good: Sanitize if HTML needed
element.innerHTML = DOMPurify.sanitize(userComment);
React/JSX
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.
- 2mo ago First seen · 346 lines · 28 tokens per session scan A 14b712728a89
security-standards is a skill published in the GitHub repository shwilliamson/automatasaurus (5 stars, last pushed 8mo ago), licensed MIT. It adds 28 tokens to every session and 1,883 once invoked, about $0.0001 per session on Opus 5.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.
security-standards compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| security-standardsshwilliamson/automatasaurus | Skill | 5 | 8mo ago | MIT | A | 28 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |