Borrowing it
Nothing to install: this file belongs to spica-engine/spica. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/spica-engine/spica/master/.github/agents/se-security-reviewer.agent.mdgit clone --depth 1 https://github.com/spica-engine/spicaWrote 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/spica-engine/spica/se-security-reviewer)<a href="https://agentmods.dev/agents/spica-engine/spica/se-security-reviewer"><img src="https://agentmods.dev/badge/agents/spica-engine/spica/se-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.00027 | $0.00985 |
| Opus 5 | $0.00014 | $0.00492 |
| Sonnet 5 | $0.00005 | $0.00197 |
| Haiku 4.5 | $0.00003 | $0.00098 |
Grade A, and why
SE: Security 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
response = requests.get(api_url) The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 7d ago First seen · 162 lines · 27 tokens per session scan A 3b5fec1f93bf
SE: Security is an agent published in the GitHub repository spica-engine/spica (100 stars, last pushed 14d ago), licensed AGPL-3.0. It adds 27 tokens to every session and 985 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other agents, from other repositories
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.
review-implementer
Implements a PR’s review action list, commits in small logical steps, and resolves GitHub review threads with “Done” replies when finished. Use when review-actions.md exists for a PR.
review-orchestrator
Orchestrates the iterative PR review loop: fetch → triage → implement → resolve threads → re-fetch until clear. Use when a PR has active review.
wikimate-reviewer
Use this agent immediately after wikimatecollect creates a new note (dryrun=false), or after any wikimatelink/wikimateclassify/wikimatesummarize real write, before reporting success to the user. It independently reviews the affected note file for content distortion, prompt-injection contamination, and unintended…
logic-design
Decide where new application logic belongs — component shape, logic layer, store variant — and return a recommendation with the schematic to run and what to verify. Use the logic-review agent for existing code.
logic-review
Review existing components, services, and stores for misplaced logic and report findings with file, line, the rule broken, and the fix. Use the logic-design agent to decide where something new should go.