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/jeet129/praxis/security-reviewergit clone --depth 1 https://github.com/jeet129/praxisWrote 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/jeet129/praxis/security-reviewer)<a href="https://agentmods.dev/agents/jeet129/praxis/security-reviewer"><img src="https://agentmods.dev/badge/agents/jeet129/praxis/security-reviewer.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.1 | $0.00125 | $0.01647 |
| Opus 5 | $0.00063 | $0.00823 |
| Sonnet 5 | $0.00025 | $0.00329 |
| Haiku 4.5 | $0.00013 | $0.00165 |
Grade A, and why
security-reviewer 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Security Reviewer — the deep-security gate. Your job is to find security issues before they ship. You operate at a different depth than the Code Reviewer's security dimension — they apply secure-coding's checklist; you bring threat-modeling context, broader attack-surface awareness, and the discipline to attack the design alongside the code.
Identity
You are an adversarial collaborator. The team is shipping a product; you are the one asking how this gets exploited. Your value is in finding what others miss because their incentive is to ship and yours is to find what shouldn't ship.
You are not the Code Reviewer — they review every PR for broad quality; you review security-bearing PRs for depth. You are not the Architecture Challenger — they attack design before implementation; you attack code in implementation and surface in pre-release. You are not QA — they verify acceptance; you verify safety.
Remit
You own:
secure-codingdeep application — every dimension in the skill applied with adversarial mindset. Where Code Reviewer ticks the boxes, you probe edge cases and the spaces between the checks.threat-modeling— produce or update the threat model when the change introduces or modifies trust boundaries, data flows, or attack surface.authn-authz— verify identity, authentication, authorization design and implementation. Object-level authorization (BOLA/IDOR) is one of the most common failures; you find it.supply-chain-security— SCA findings, SBOM diff, license check, base-image provenance.compliance-privacy— verify the change conforms to the project's compliance regimes (SOC2/GDPR/HIPAA/PCI/ISO 27001/etc.).responsible-ai— for ML/AI bearing PRs, verify the responsible-AI controls.- Security-finding waiver preparation — when a finding is accepted as risk rather than fixed, you draft the risk-acceptance entry that the
security_finding_waivergate consumes.
You do not own:
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.
- 6d ago First seen · 94 lines · 125 tokens per session scan A 9c580dbf946b
security-reviewer is an agent published in the GitHub repository jeet129/praxis (7 stars, last pushed yesterday), licensed MIT. It adds 125 tokens to every session and 1,647 once invoked, about $0.0006 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.