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 commands/sinewaveai/agent-security-scanner-mcp/fix-securitygit clone --depth 1 https://github.com/sinewaveai/agent-security-scanner-mcpWrote 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/commands/sinewaveai/agent-security-scanner-mcp/fix-security)<a href="https://agentmods.dev/commands/sinewaveai/agent-security-scanner-mcp/fix-security"><img src="https://agentmods.dev/badge/commands/sinewaveai/agent-security-scanner-mcp/fix-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 | $0.00000 | $0.00422 |
| Opus 5 | $0.00000 | $0.00211 |
| Sonnet 5 | $0.00000 | $0.00084 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
fix-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 4d 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
Fix Security Issues
Analyze the current file for security vulnerabilities detected by the Agent Security extension and automatically apply fixes.
Instructions
- First, get all diagnostics for the current file using the IDE diagnostics tool
- Filter for diagnostics where
sourceis "Agent Security" - For each security issue found, analyze the code and apply the appropriate fix based on the rule ID
Fix Strategies by Rule Type
SQL Injection (sql-injection, sqli)
- Convert string concatenation to parameterized queries
- Replace f-strings/template literals with placeholders
- Use prepared statements
XSS (innerHTML, outerHTML, dangerouslySetInnerHTML)
- Replace
.innerHTMLwith.textContentfor plain text - Add DOMPurify.sanitize() wrapper for HTML content
- Use safe DOM methods like createElement/appendChild
Command Injection (exec, subprocess, shell=True)
- Replace
exec()withexecFile()orspawn() - Change
shell=Truetoshell=False - Split command strings into argument arrays
Hardcoded Secrets (password, api_key, secret)
- Replace hardcoded values with environment variables
- Use
process.env.VAR_NAME(JS) oros.environ.get('VAR_NAME')(Python)
Weak Cryptography (md5, sha1)
- Replace MD5/SHA1 with SHA-256 or stronger
- Use
hashlib.sha256()(Python) orcrypto.createHash('sha256')(JS)
Insecure Deserialization (pickle, yaml.load)
- Replace
pickle.loadwithjson.load - Replace
yaml.load()withyaml.safe_load()
SSL/TLS Issues (verify=False, rejectUnauthorized)
- Set
verify=Trueor remove the insecure option - Enable certificate verification
Task
Read the current file, identify all security issues from the Agent Security extension diagnostics, and apply fixes directly to the code. After fixing, briefly explain what was changed.
$ARGUMENTS
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.
- 4d ago First seen · 49 lines · 0 tokens per session scan A 375d86633933
fix-security is a command published in the GitHub repository sinewaveai/agent-security-scanner-mcp (121 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 422 tokens. 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 commands, from other repositories
xpoz-best-practices
Reference docs for Xpoz query syntax, pagination, field selection, platform tools, and authentication. Usage: /xpoz-best-practices.
xpoz-track
Manage tracked keywords, users, subreddits, and hashtags across Twitter, Instagram, Reddit, and TikTok. Usage: /xpoz-track.
qring:dashboard
Start the q-ring local status dashboard (SSE + browser UI). Use when the user wants a live view of secret health, manifest gaps, policy posture, approvals, hooks, and audit traffic without exposing secret values.
xpoz-setup
Configure the Xpoz MCP connection and verify your account. Usage: /xpoz-setup.
qring-setup-project
Initialize q-ring for the current project — detect environment, create manifest, import .env, set up hooks.
qring-scan-secrets
Scan the workspace for hardcoded secrets, then offer to auto-fix them with q-ring.