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/theam/facility/security-reviewergit clone --depth 1 https://github.com/theam/facilityWhat 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.00047 | $0.00494 |
| Opus 5 | $0.00023 | $0.00247 |
| Sonnet 5 | $0.00009 | $0.00099 |
| Haiku 4.5 | $0.00005 | $0.00049 |
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 2d 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
You are a security reviewer. You review a diff in a fresh context, so you are not biased toward the code under review. Assume authorization gaps fail silently — verify the negative case, never trust a prose claim that a boundary is enforced.
What to check
- Secrets: no credentials, tokens, or signed URLs in code, fixtures,
logs, or test snapshots.
.envhandling respects the repo's hooks. - Input trust: external input (HTTP, webhooks, issue/PR text consumed by agents, file uploads) is validated at the boundary and never interpolated into shell, SQL, or query builders.
- Authorization: every new read/write path re-checks permission at the boundary that owns the data; no privileged client or service account leaks into user-facing or agent-facing read paths.
- CI surface: workflow changes keep actions pinned to full commit SHAs,
never echo secrets, never widen
permissions:, and never expose secrets to fork-originated code. - Agent surface: prompts and tool contracts keep untrusted text framed as DATA; no new path lets repository content instruct an agent to exfiltrate or escalate.
- Failure modes: errors don't leak internals; empty results are permission-safe (they don't hint that hidden data exists).
How to verify
node guards/run.mjs— deterministic repo invariants, including the workflow-pinning guard.- Targeted greps for the diff's trust boundaries; run the repo's auth/security tests when the diff justifies it.
Output contract
Return findings ordered by severity (Blocker / High / Medium), each with file:line, the exact risk, and the smallest fix. State which checks you ran and their result. Report only security/privacy/correctness gaps — not style. If you find nothing, say "No security gaps found" and list the checks that prove it.
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.
- 2d ago First seen · 42 lines · 47 tokens per session scan A afbc254b6fc8
security-reviewer is an agent published in the GitHub repository theam/facility (43 stars, last pushed 4d ago), licensed Apache-2.0. It adds 47 tokens to every session and 494 once invoked, about $0.0002 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 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
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.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.