infosec-engineer

infosec-engineer is a skill for Claude Code from CrashBytes/claude-role-skills. It costs 138 tokens per session (2,487 once invoked), scanned A, original, Apache-2.0.

An information-security review assistant for assessing software, infrastructure, and processes. It covers threat modeling, vulnerability checks, compliance reviews, and incident-response planning.

In plain words
What is it for?
Use it to review security architecture, model threats with methods such as STRIDE and DREAD, assess vulnerabilities, check compliance, and plan responses to incidents.
Why use it?
It helps find security risks and weak points before they cause harm, while connecting technical issues to practical business needs.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the role-based-skills plugin — 7 skills, 15 commands shipped together

Good fit Use it to review security architecture, model threats with methods such as STRIDE and DREAD, assess vulnerabilities, check compliance, and plan responses to incidents.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/crashbytes/claude-role-skills/infosec-engineer
Install

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.

Any agent
npx skills add CrashBytes/claude-role-skills --skill infosec-engineer
Clone the repo
git clone --depth 1 https://github.com/CrashBytes/claude-role-skills

Made for: Claude Code.

Or install role-based-skills, the plugin that ships this one along with the rest of its 7 skills, 15 commands.

Wrote 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.

agentmods badge for infosec-engineer

README.md
[![agentmods](https://agentmods.dev/badge/skills/crashbytes/claude-role-skills/infosec-engineer/github.svg)](https://agentmods.dev/skills/crashbytes/claude-role-skills/infosec-engineer)
Your own site
<a href="https://agentmods.dev/skills/crashbytes/claude-role-skills/infosec-engineer"><img src="https://agentmods.dev/badge/skills/crashbytes/claude-role-skills/infosec-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.

agentmods 80×15 button for infosec-engineer

Your own site · 80×15
<a href="https://agentmods.dev/skills/crashbytes/claude-role-skills/infosec-engineer"><img src="https://agentmods.dev/badge/skills/crashbytes/claude-role-skills/infosec-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 138 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,487 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00138 $0.02487
Opus 5 $0.00069 $0.01243
Sonnet 5 $0.00028 $0.00497
Haiku 4.5 $0.00014 $0.00249

Measured 10d ago against content hash 0dbfee41f54e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

infosec-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 10d 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.

skills/infosec-engineer/SKILL.md · 241 lines

How it starts

The opening of the file, as written. The whole thing — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.

InfoSec Engineer

Act as an experienced Information Security Engineer who takes a risk-based, practical approach to security. Balance security rigor with business needs — secure solutions should be usable, not just compliant.

Core Responsibilities

  1. Assess and reduce risk through threat modeling and security reviews
  2. Identify and remediate vulnerabilities in code, infrastructure, and processes
  3. Ensure compliance with relevant frameworks and regulations
  4. Plan and execute incident response procedures
  5. Build security culture through education and process integration

Threat Modeling

STRIDE Framework

Analyze threats by category:

Threat Property Violated Question to Ask
Spoofing Authentication Can an attacker pretend to be someone/something else?
Tampering Integrity Can an attacker modify data in transit or at rest?
Repudiation Non-repudiation Can an attacker deny performing an action?
Information Disclosure Confidentiality Can an attacker access data they shouldn't?
Denial of Service Availability Can an attacker prevent legitimate use?
Elevation of Privilege Authorization Can an attacker gain higher access than granted?

Threat Modeling Process

  1. Define scope — What system/feature is being modeled?
  2. Draw a data flow diagram — Show trust boundaries, data stores, processes, data flows
  3. Identify threats — Apply STRIDE to each element crossing a trust boundary
  4. Rate risk — Use DREAD or risk matrix (likelihood × impact)
  5. Define mitigations — For each threat, identify controls
  6. Validate — Review with engineering and security team

DREAD Risk Rating

Rate each factor 1-10:

  • Damage — How bad is the impact?
  • Reproducibility — How easy to reproduce?
  • Exploitability — How easy to exploit?
  • Affected Users — How many users impacted?
  • Discoverability — How easy to find the vulnerability?

Read the full file on GitHub · 241 lines

Files

What ships with it

5 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.

Changes

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.

  1. 10d ago First seen · 241 lines · 138 tokens per session scan A 0dbfee41f54e

Subscribe to this mod's changes

infosec-engineer is a skill published in the GitHub repository CrashBytes/claude-role-skills (6 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 138 tokens to every session and 2,487 once invoked, about $0.0007 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.

Related

Other skills, from other repositories

chief-strategy-officer

Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business…

cbrock84/headcount · 93 tokens

seo-strategy

Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions that determine what can rank. Use this to run an SEO audit, diagnose why pages are not ranking or were deindexed, plan a site's URL and navigation structure, add structured…

cbrock84/headcount · 74 tokens

service-desk

Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…

cbrock84/headcount · 73 tokens

youtube-producer

Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosing why a video or channel underperforms. Use this for video ideas, packaging, scripting, a retention teardown, or channel strategy — including when someone describes a…

cbrock84/headcount · 86 tokens

support-operations

Designs and runs the support function — channels, queues, routing, staffing, service levels, quality, and the metrics that show whether it is working. Use this to set up or fix support operations, choose channels, size a team, set or renegotiate service levels, reduce cost per contact, diagnose long queues or poor…

cbrock84/headcount · 77 tokens

voice-of-customer

Builds the loop from what customers say to what gets changed — collecting feedback, distinguishing signal from noise, routing it to owners, and closing the loop back to the customer. Use this to set up a feedback program, design or interpret CSAT/NPS, decide what customer feedback deserves action, get product to act…

cbrock84/headcount · 82 tokens