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 agents/jsk9999/ai-nexus/security-rulesgit clone --depth 1 https://github.com/JSK9999/ai-nexusWrote 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/agents/jsk9999/ai-nexus/security-rules)<a href="https://agentmods.dev/agents/jsk9999/ai-nexus/security-rules"><img src="https://agentmods.dev/badge/agents/jsk9999/ai-nexus/security-rules.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.00013 | $0.00410 |
| Opus 5 | $0.00006 | $0.00205 |
| Sonnet 5 | $0.00003 | $0.00082 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade A, and why
Security Rules 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 3d 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 Rules
ABSOLUTE Rules (NEVER Violate)
NEVER
- Leave secrets (passwords/API keys/tokens) in code/logs/tickets/environment variables/.env files.
- Log sensitive data (PII/credit cards/SSN) in logs.
- Leave SQL injection, XSS, CSRF vulnerabilities.
- Commit secrets, API keys, tokens, or sensitive information.
ALWAYS
- Validate, normalize, and encode all inputs; use parameterized queries.
- Use HTTPS/TLS and apply principle of least privilege.
- Apply authentication/authorization to all endpoints.
- Set security headers (CSP, HSTS, X-Frame-Options).
- Regularly scan and update dependency vulnerabilities.
Security Violation Protocol
Stop work immediately and request review upon security violations.
Pre-commit Security Checklist
- No secrets (passwords/API keys/tokens) in code
- No sensitive data (PII/credit cards/SSN) in logs
- No SQL injection vulnerabilities
- No XSS vulnerabilities
- No CSRF vulnerabilities
- All inputs validated and sanitized
- Parameterized queries used for database operations
- Authentication/authorization applied to endpoints
- Development debug code removed
- Console logs cleaned up
Common Vulnerability Prevention
| Vulnerability | Prevention |
|---|---|
| SQL Injection | Use parameterized queries, ORMs |
| XSS | Encode output, use CSP headers |
| CSRF | Use CSRF tokens, SameSite cookies |
| Auth Bypass | Validate on server, check permissions |
| Data Exposure | Minimize data, encrypt at rest/transit |
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.
- 3d ago First seen · 52 lines · 13 tokens per session scan A 9954a63e103c
Security Rules is an agent published in the GitHub repository JSK9999/ai-nexus (18 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 410 once invoked, about $0.0001 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 agents, from other repositories
security-auditor
Security auditor: vulnerability scanning, dependency audits, OWASP Top 10 compliance, secrets detection, remediation.
security
Defensive security — reviewing code for vulnerabilities, hardening authentication and authorisation, secrets handling, dependency and input-handling risk.
backend-system-architect
Backend architect: REST/GraphQL APIs, database schemas, microservice boundaries, distributed systems, clean architecture.
security-reviewer
Security vulnerability detection and remediation specialist.
Technical Manager
Engineering manager that coordinates all agents, tracks progress, prioritizes work, and surfaces decisions to the human operator.
QA Engineer
Quality assurance and test engineer. Writes tests, validates acceptance criteria, tracks coverage, and performs gap analysis.