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/srajangpt1/ai-security-crew/verify-codegit clone --depth 1 https://github.com/Srajangpt1/ai-security-crewWrote 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/srajangpt1/ai-security-crew/verify-code)<a href="https://agentmods.dev/commands/srajangpt1/ai-security-crew/verify-code"><img src="https://agentmods.dev/badge/commands/srajangpt1/ai-security-crew/verify-code.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.01065 |
| Opus 5 | $0.00000 | $0.00532 |
| Sonnet 5 | $0.00000 | $0.00213 |
| Haiku 4.5 | $0.00000 | $0.00106 |
Grade A, and why
verify-code scanned grade A with 1 finding 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- Command injection via `os.system()`, `subprocess` with `shell=True` How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Perform a security review of the following code:
$ARGUMENTS
Instructions
Review the code provided in the arguments above for security vulnerabilities. If no code is provided in the arguments, ask the user to paste the code they want reviewed, or specify a file path to read.
Step 1 — Detect Technologies
Identify the language and frameworks from:
- File extension (
.py→ Python,.ts→ TypeScript,.go→ Go, etc.) - Import statements (
import django,require('express'),import React, etc.) - Syntax patterns (
def/class→ Python,func→ Go,public class→ Java) - Framework indicators (
@app.route→ Flask,useState→ React,@Controller→ Spring)
Step 2 — Build Focus Areas
Based on detected technologies, check for these vulnerability classes:
Python:
- Command injection via
os.system(),subprocesswithshell=True - Unsafe deserialization:
pickle.loads()on untrusted data eval()/exec()with dynamic/user-controlled input- SQL injection via string formatting in queries
- Path traversal in file operations
JavaScript / TypeScript:
- XSS via
innerHTML,document.write(),dangerouslySetInnerHTML - Prototype pollution via object spread or
Object.assign eval()ornew Function()with dynamic content- Insecure
postMessagehandlers - Unvalidated redirects
React:
dangerouslySetInnerHTMLwithout sanitization- User input rendered directly in JSX
- Sensitive data stored in component state or localStorage
Java:
Statementinstead ofPreparedStatementfor SQLRuntime.exec()with user-controlled input- XML External Entity (XXE) vulnerabilities
- Unsafe deserialization
Go:
- SQL injection in raw queries
- Command injection in
exec.Command - Path traversal in file serving
- Race conditions in concurrent code
SQL:
- String concatenation in queries instead of parameterization
- Missing
WHEREclause onUPDATE/DELETE SELECT *returning sensitive columns- Privilege escalation via stored procedures
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 · 150 lines · 0 tokens per session scan A cc51995d7bae
verify-code is a command published in the GitHub repository Srajangpt1/ai-security-crew (68 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,065 tokens. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.