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 skills/igor9silva/meseeks/convex-security-checknpx skills add igor9silva/meseeks --skill convex-security-checkgit clone --depth 1 https://github.com/igor9silva/meseeksWrote 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/skills/igor9silva/meseeks/convex-security-check)<a href="https://agentmods.dev/skills/igor9silva/meseeks/convex-security-check"><img src="https://agentmods.dev/badge/skills/igor9silva/meseeks/convex-security-check.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.00027 | $0.02332 |
| Opus 5 | $0.00014 | $0.01166 |
| Sonnet 5 | $0.00005 | $0.00466 |
| Haiku 4.5 | $0.00003 | $0.00233 |
Grade A, and why
convex-security-check 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 5d 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.
Sends data to an external URLlowData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
const response = await fetch("https://api.resend.com/emails", { method: "POST", Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
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.
- 5d ago First seen · 379 lines · 27 tokens per session scan A bd7df401693d
convex-security-check is a skill published in the GitHub repository igor9silva/meseeks (20 stars, last pushed 1mo ago), licensed AGPL-3.0. It adds 27 tokens to every session and 2,332 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (sends data to an external url). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
convex-security-check
Quick security audit checklist covering authentication, function exposure, argument validation, row-level access control, and environment variable handling.
convex-security-check
Quick security audit checklist covering authentication, function exposure, argument validation, row-level access control, and environment variable handling.
Convex Security Check
Quick security audit checklist covering authentication, function exposure, argument validation, row-level access control, and environment variable handling.
convex-security-check
Quick security audit checklist covering authentication, function exposure, argument validation, row-level access control, and environment variable handling.
Convex Security Check
Quick security audit checklist covering authentication, function exposure, argument validation, row-level access control, and environment variable handling.
db
Database schema and query conventions for ThunderID. Use when changing schema scripts, defining SQL queries, updating store constants, or reviewing deployment-scoped persistence rules.