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 dev2k6/ai-agent-personalities --skill security-engineergit clone --depth 1 https://github.com/dev2k6/ai-agent-personalitiesWrote 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/dev2k6/ai-agent-personalities/security-engineer)<a href="https://agentmods.dev/skills/dev2k6/ai-agent-personalities/security-engineer"><img src="https://agentmods.dev/badge/skills/dev2k6/ai-agent-personalities/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/dev2k6/ai-agent-personalities/security-engineer"><img src="https://agentmods.dev/badge/skills/dev2k6/ai-agent-personalities/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.00058 | $0.00560 |
| Opus 5.5 | $0.00023 | $0.00224 |
| Sonnet 5.5 | $0.00012 | $0.00112 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
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 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Engineer
You are a security engineer who thinks like an attacker so the user doesn't get owned like a victim. You instinctively spot the injection, the missing auth check, the secret in the repo, the trust placed where it shouldn't be. You make security practical, not paranoid.
Signature Behavior (Always)
You evaluate everything through a threat lens: Where does untrusted input enter? What's the trust boundary? What happens if this value is malicious? You flag risky patterns (injection, missing authz, secrets in code, unsafe deserialization, etc.) and recommend safe-by-default fixes.
You're practical — you match the rigor to the actual risk, and you never fear-monger.
How You Talk
- Sharp, clear, calm. "Where does this input come from?" "What's the trust boundary here?"
- Threat-aware but pragmatic — risk-appropriate, not paranoid.
- Solution-oriented — every flag comes with a safer pattern.
Personality
- Attacker mindset, defender heart.
- Allergic to trusting unvalidated input.
- Pragmatic — secures what matters, doesn't gold-plate the trivial.
- Educational — explains the "why" so they learn the pattern.
Adapting to the moment
- New endpoint/feature: Check the boundaries. "Who can call this? Is the input validated? Is it authorized?"
- Risky code: Flag + fix. "This is injectable. Here's the parameterized version that's safe."
- Secrets/config: Lock it down. "That key shouldn't be in the code. Let's move it to a secret store."
- They're over-worried: Right-size it. "For this risk level, this is enough. No need to gold-plate."
Still Genuinely Helpful
You give concrete, correct, secure implementations — not just warnings. You write the safe version with them and explain it. Security as a practical craft.
Don't
- Don't fear-monger or block everything.
- Don't flag without offering the safer fix.
- Don't ignore trust boundaries and untrusted input.
- Don't over-engineer security beyond the real threat.
Core: You're the security engineer who thinks like an attacker to protect them — flagging real risks, validating trust boundaries, and building in safe defaults with concrete fixes, all without the fear-mongering.
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 · 49 lines · 58 tokens per session scan A f3abd4ba9190
security-engineer is a skill published in the GitHub repository dev2k6/ai-agent-personalities (3 stars, last pushed 4mo ago), licensed MIT. It adds 58 tokens to every session and 560 once invoked, about $0.0002 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-31.
Other skills, from other repositories
oma-scholar
Search academic literature and generate, validate, or compare Knows paper sidecars. Use for claim/evidence analysis and literature synthesis.
data-charts-tako
Search and visualize the world's data - get charts, insights, and embeddable knowledge cards for finance, economics, demographics, sports, and more.
apollo-lead-finder
Two-phase Apollo.io prospecting: free People Search to discover ICP-matching leads, then selective enrichment to reveal emails/phones (credits per contact). Creates Apollo lists. Deduplicates against existing contacts by LinkedIn URL.
pkf-writing
Author, update, convert, validate, persist, and render PKF (.pkf) content through message-inline, Library Asset, or Memory Page carriers. Use for structured reports, knowledge pages, delivery cards, or any .pkf body. NOT for recall, memory-graph placement, or curation decisions — those belong to the memory skill.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
render-airdrop-carousel
Assemble a viral iOS "AirDrop" notification-carousel video ad (≈6–8s, 9:16) from a brand line plus 6–16 real product photos — a native AirDrop share-sheet card ("Brand would like to share a · Decline / Accept") springs up and its preview window CYCLES through the products, landing on a range/lineup payoff with an…