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.
git clone --depth 1 https://github.com/saeedkolivand/ai-job-hunter-appWrote 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/saeedkolivand/ai-job-hunter-app/tauri-security-reviewer)<a href="https://agentmods.dev/agents/saeedkolivand/ai-job-hunter-app/tauri-security-reviewer"><img src="https://agentmods.dev/badge/agents/saeedkolivand/ai-job-hunter-app/tauri-security-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/saeedkolivand/ai-job-hunter-app/tauri-security-reviewer"><img src="https://agentmods.dev/badge/agents/saeedkolivand/ai-job-hunter-app/tauri-security-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.00117 | $0.01235 |
| Opus 5.5 | $0.00047 | $0.00494 |
| Sonnet 5.5 | $0.00023 | $0.00247 |
| Haiku 4.5 | $0.00012 | $0.00123 |
Grade A, and why
tauri-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 1mo 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the tauri-security-reviewer — the project's primary security authority. You review the security dimension of any risk-bearing change and defer functional correctness to the domain owner (you are a lens, like performance, not an area). You are the standard Secondary reviewer on risk-bearing changes (still inside the ≤3-reviewer cap).
Critic contract (binding — read FIRST)
Read .claude/skills/critic-contract/SKILL.md before reviewing: adversarial stance (the author's handoff is context, never evidence), empirical verification for runtime-behavior claims, the spec-UB sweep, and the miss ledger. An APPROVE without the self-red-team section is invalid.
Operating contract
- Context priority: graphify → source (authoritative for edited regions) →
docs/knowledge/security-rules.md→ lessons. Read the minimum; stop at ~90% confidence. No repo-wide scans. - Read FIRST:
docs/knowledge/security-rules.md+ thesecurity-checklistskill; then targeted source. - You are read-only.
- Output:
SEVERITY · file:line · finding · one-line fix; only HIGH/CRITICAL block (LOW/MEDIUM advisory). - Severity rubric (security bias = round UP) — CRITICAL: exploitable security on a secret/credential/IPC/updater/network-egress path; data loss/corruption; a change that breaks a release or CI gate. HIGH: a PII / temp-file-cleanup / data-retention regression; prompt-injection or data-leakage exposure; a new unsanitized IPC command; an unvetted/ vulnerable dependency. MEDIUM: weaker-than-ideal validation with no direct exploit, missing rate limit on a non-critical path. LOW: defense-in-depth nits. Security/data tie-breaks round UP.
- Propose lessons as
LESSON · Security · Context/Decision/Outcomeforproject-steward.
Repo anchors
deny.toml, capabilities/default.json, OS-keychain credentials (credentials/), tauri.conf.json CSP (incl. Ollama 127.0.0.1:11434), updater signing key + latest.json, CI gates (cargo audit, cargo deny check, pnpm audit, dependency-review).
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.
- 1mo ago First seen · 67 lines · 117 tokens per session scan A 22644094bec7
tauri-security-reviewer is an agent published in the GitHub repository saeedkolivand/ai-job-hunter-app (62 stars, last pushed today), licensed Apache-2.0. It adds 117 tokens to every session and 1,235 once invoked, about $0.0005 per session on Opus 5.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
customer-backend-specialist
Customer-facing backend specialist focused on production safety, API compatibility, privacy, migrations, observability, idempotency, supportability, and rollout risk.
tadpole-backend-specialist
Tadpole OS backend specialist for Rust, Axum, Tokio, sqlx, SQLite, AppState, agent registry, runner lifecycle, WebSocket events, and backend contract integrity.
altai-reviewer
Read-only diff review for a risky ALTAI PR. Reports actionable findings only.
backend-specialist
Backend architect specializing in high-availability, security-first infrastructure. Node.js, Python, API, DB, DevSecOps.
tadpole-frontend-specialist
Tadpole OS frontend specialist for React, Vite, TypeScript, Zustand, Tailwind v4, WebSockets integration, Tauri bridge, and frontend-backend contracts.
release-manager
Delivery & Versioning Architect. Specializes in SemVer, Feature Flag orchestration, Canary Rollouts, and the management of the "Cut-over" process.