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/alirezasoltanijazi/skillnir/securityengineernpx skills add AlirezaSoltaniJazi/Skillnir --skill securityengineergit clone --depth 1 https://github.com/AlirezaSoltaniJazi/SkillnirWrote 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/alirezasoltanijazi/skillnir/securityengineer)<a href="https://agentmods.dev/skills/alirezasoltanijazi/skillnir/securityengineer"><img src="https://agentmods.dev/badge/skills/alirezasoltanijazi/skillnir/securityengineer.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.00079 | $0.03434 |
| Opus 5 | $0.00039 | $0.01717 |
| Sonnet 5 | $0.00016 | $0.00687 |
| Haiku 4.5 | $0.00008 | $0.00343 |
Grade A, and why
securityEngineer 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 4d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Before You Start
Read LEARNED.md first. It contains corrections, preferences, and conventions accumulated from previous sessions. Apply every rule in that file — they override defaults in this skill.
Announce skill usage. Always say "Using: securityEngineer skill" at the very start of your response before doing any work.
This skill is READ-ONLY. Security analysis never modifies code. Remediation is suggested with code examples — never silently applied.
When to Use
- Security audit or vulnerability assessment of any project component
- Pre-deploy security review or compliance check (OWASP, NIST, CIS)
- Dependency audit, CVE triage, or supply chain risk assessment
- Secret scanning, credential review, or cryptographic implementation review
- Incident investigation or penetration test report review
- Code review with security focus (injection, auth, access control)
Do NOT Use
- Python backend development (API design, CLI logic, async patterns) — use backendEngineer
- NiceGUI UI components/pages (Tailwind, Quasar, HTML) — use frontendEngineer
- CI/CD, Docker, pre-commit hooks, workflows — use devopsEngineer
- Skill system meta-rules (SKILL.md structure, LEARNED.md format) — use skillnir
Vulnerability Classification
| Severity | CVSS Score | Response | Format |
|---|---|---|---|
| Critical | ≥ 9.0 | Immediate — block release | CRITICAL: CWE-XXX — description |
| High | 7.0–8.9 | Fix before next deploy | HIGH: CWE-XXX — description |
| Medium | 4.0–6.9 | Fix within sprint | MEDIUM: CWE-XXX — description |
| Low | 0.1–3.9 | Track and fix when convenient | LOW: CWE-XXX — description |
| Info | 0.0 | Document for awareness | INFO: description |
What ships with it
17 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/config-auditor.md 1.6 KB
- agents/dependency-auditor.md 1.6 KB
- agents/pentest-reviewer.md 1.6 KB
- agents/vulnerability-scanner.md 1.5 KB
- assets/csp-policy-example.json 605 B
- assets/security-headers-example.conf 1.7 KB
- INJECT.md 897 B
- LEARNED.md 528 B
- references/ai-interaction-guide.md 1.8 KB
- references/code-style.md 1.8 KB
- references/common-issues.md 2.1 KB
- references/owasp-mapping.md 2.4 KB
- references/remediation-templates.md 3.1 KB
- references/report-template.md 2.5 KB
- references/security-checklist.md 4.6 KB
- references/vulnerability-patterns.md 6.5 KB
- scripts/validate-security.sh 3.1 KB runs code
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.
- 4d ago First seen · 205 lines · 79 tokens per session scan A a7eb700a9d6c
securityEngineer is a skill published in the GitHub repository AlirezaSoltaniJazi/Skillnir (7 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 3,434 once invoked, about $0.0004 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…