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 batterfried-philosophy172/Agent-Startup-Skills --skill security-auditor-saasgit clone --depth 1 https://github.com/batterfried-philosophy172/Agent-Startup-SkillsWrote 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/batterfried-philosophy172/agent-startup-skills/security-auditor-saas)<a href="https://agentmods.dev/skills/batterfried-philosophy172/agent-startup-skills/security-auditor-saas"><img src="https://agentmods.dev/badge/skills/batterfried-philosophy172/agent-startup-skills/security-auditor-saas/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/batterfried-philosophy172/agent-startup-skills/security-auditor-saas"><img src="https://agentmods.dev/badge/skills/batterfried-philosophy172/agent-startup-skills/security-auditor-saas.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.00053 | $0.00751 |
| Opus 5 | $0.00026 | $0.00376 |
| Sonnet 5 | $0.00011 | $0.00150 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
security-auditor-saas 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 11d 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.
This is a copy
100% identical to security-auditor-saas — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Auditor — Hardening Agent
Purpose
Identify and remediate security vulnerabilities before the product is deployed. Prevent data breaches, unauthorized access, and common attack vectors.
When to Use
- After code and tests are complete
- Before deployment planning
- When the user asks "is this code secure?"
Audit Checklist (OWASP Top 10 Aligned)
1. Injection (SQL, NoSQL, Command)
- All database queries use parameterized statements or ORM
- No string concatenation in queries
- User input is never passed directly to system commands
2. Broken Authentication
- Passwords are hashed with bcrypt/argon2 (never plain text, never MD5/SHA)
- Sessions expire after a reasonable timeout
- Login has rate limiting or brute-force protection
- Password reset tokens are single-use and time-limited
3. Sensitive Data Exposure
- No secrets in source code (API keys, passwords, tokens)
-
.envfiles are in.gitignore - HTTPS is enforced in production
- Sensitive data is not logged
4. Broken Access Control
- Users cannot access other users' data by changing IDs in URLs
- Admin routes are protected with role checks
- API endpoints verify the requesting user's permissions
5. Security Misconfiguration
- CORS is configured to allow only known origins
- Debug mode is disabled in production config
- Default credentials are changed
- Error messages do not expose stack traces to users
6. Cross-Site Scripting (XSS)
- All user-generated content is escaped/sanitized before rendering
- Content-Security-Policy headers are set
- React/Vue/Angular auto-escaping is not bypassed (no dangerouslySetInnerHTML)
7. Cross-Site Request Forgery (CSRF)
- CSRF tokens are used on state-changing forms
- SameSite cookie attribute is set
8. Insecure Dependencies
- No known vulnerable dependencies (check npm audit / pip audit)
- Dependencies are pinned to specific versions
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.
- 11d ago First seen · 92 lines · 53 tokens per session scan A 1a63c46ef01b
security-auditor-saas is a skill published in the GitHub repository batterfried-philosophy172/Agent-Startup-Skills (2 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session and 751 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to security-auditor-saas, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
import
Import a self-contained NeatContext context bundle shared by another person, or reconcile a newer copy of a context already on this machine, leaving the source bundle unchanged. Use only when the user explicitly invokes this skill or asks to import a NeatContext bundle.
save
Save durable decisions, findings, plans, and implementation knowledge from the visible Codex conversation into a new or existing NeatContext context. Use only when the user explicitly invokes this skill or asks to preserve the current conversation as reusable context.
create
Create a fresh NeatContext context from a user-defined behavioral profile and an existing local knowledge folder. Use only when the user explicitly invokes this skill or asks to create a new context rather than save the current conversation.
extensions
Report which extensions the connected NeatContext context expects, and whether this machine provides them. Use when the user asks what a context can reach, why an extension tool is missing, or how to connect one here.
delete
Preview and permanently delete a NeatContext context while preserving any externally linked knowledge folder. Use only when the user explicitly invokes this skill or clearly asks to delete a context.
export
Export a NeatContext context saved from a conversation into a self-contained bundle folder that can be shared or moved to another machine. Use only when the user explicitly invokes this skill or asks to export a NeatContext context.