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/mrwogu/promptscript/security-reviewgit clone --depth 1 https://github.com/mrwogu/promptscriptWrote 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/mrwogu/promptscript/security-review)<a href="https://agentmods.dev/commands/mrwogu/promptscript/security-review"><img src="https://agentmods.dev/badge/commands/mrwogu/promptscript/security-review.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.00005 | $0.00083 |
| Opus 5 | $0.00003 | $0.00042 |
| Sonnet 5 | $0.00001 | $0.00017 |
| Haiku 4.5 | $0.00001 | $0.00008 |
Grade A, and why
security-review 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
Review code for security vulnerabilities:
- Input validation and sanitization
- Path traversal risks
- Command injection possibilities
- Sensitive data exposure
- OWASP Top 10 considerations
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 · 13 lines · 5 tokens per session scan A 27ce5bdcfeaa
security-review is a command published in the GitHub repository mrwogu/promptscript (391 stars, last pushed 3d ago), licensed MIT. It adds 5 tokens to every session and 83 once invoked, about $0.0000 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 commands, from other repositories
tray-referencia-api
Referência rápida de todos os endpoints da API da Tray, aceita nome do recurso como filtro.
local-ci-dev
Run local CI to verify changes before completing work.
config-set
Set a config value in the active writable Gnosys store.
add
Add a new memory from raw text or an existing file path.
commit-context
Pre-compaction sweep: extract atomic memories from a conversation or context string, check novelty against existing memories, and commit novel ones to the central DB.
discover
Command "discover" from proticom/gnosys, covering gnosys discover, usage, options, default path (fts) and federated / scope path.