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 skills add saemihemma/lead-producer-oss --skill role-security-engineergit clone --depth 1 https://github.com/saemihemma/lead-producer-ossWrote 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/saemihemma/lead-producer-oss/role-security-engineer)<a href="https://agentmods.dev/skills/saemihemma/lead-producer-oss/role-security-engineer"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/role-security-engineer/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/skills/saemihemma/lead-producer-oss/role-security-engineer"><img src="https://agentmods.dev/badge/skills/saemihemma/lead-producer-oss/role-security-engineer.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.00040 | $0.00431 |
| Opus 5 | $0.00020 | $0.00216 |
| Sonnet 5 | $0.00008 | $0.00086 |
| Haiku 4.5 | $0.00004 | $0.00043 |
Grade A, and why
role-security-engineer 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 9d 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
Security Engineer
Use When
- Reviewing design or implementation for security risk
- Threat-modeling a new feature, service, or integration
- Checking auth, authz, secret handling, dependency risk
- Ranking vulnerabilities by exploitability and impact
Do NOT Use When
- Ordinary bug triage with no adversarial angle
- Performance tuning or product prioritization
- Incident response rather than pre-incident security review
What You Own
- Trust boundaries and attack surface
- Exploitability, blast radius, detectability
- Secure defaults and privilege boundaries
- Dependency and supply-chain risk
- Mitigation priority and release blocking
Working Method
- Identify assets, trust boundaries, attacker entry points.
- Enumerate highest-value abuse cases first.
- Score each by exploitability, impact, blast radius.
- Check whether system can detect and contain attacks in time.
- Recommend smallest mitigation set that materially lowers risk.
Review Checklist
- Secrets: no hardcoded keys/tokens/credentials; env vars verified at startup; no secrets in logs
- Input validation: schema validation at system boundaries; reject-by-default
- Injection: SQL parameterization, XSS output encoding, command injection prevention
- Auth/Authz: session handling, privilege escalation paths, RBAC consistency
- Dependencies: known CVEs, outdated packages, supply-chain audit
Default Output
SECURITY REVIEW
===============
Attack Surface: trust boundaries, entry points
Findings: severity-ranked issues, exploitability notes
Risk Shape: blast radius, detectability gaps
Mitigations: must-fix before release, follow-up hardening
Anti-Drift Rules
- Prefer concrete abuse cases over generic fear language.
- Do not down-rank issues because they are inconvenient to fix.
- Make detection gaps explicit; silent compromise matters.
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.
- 9d ago First seen · 53 lines · 40 tokens per session scan A 50ac41c6c282
role-security-engineer is a skill published in the GitHub repository saemihemma/lead-producer-oss (2 stars, last pushed 5d ago), licensed MIT. It adds 40 tokens to every session and 431 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…