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 commands/hermeticormus/libresecops-claude-code/awareness-plangit clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-CodeWrote 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/commands/hermeticormus/libresecops-claude-code/awareness-plan)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/awareness-plan"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/awareness-plan.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.1 | $0.00000 | $0.01720 |
| Opus 5 | $0.00000 | $0.00860 |
| Sonnet 5 | $0.00000 | $0.00344 |
| Haiku 4.5 | $0.00000 | $0.00172 |
Grade A, and why
awareness-plan 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 2d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/awareness-plan
Design a complete security awareness training program with phased implementation, role-based content, simulation calendar, and measurable outcomes.
Trigger
Use when building or overhauling a security awareness program. Appropriate for:
- Establishing a new awareness program from scratch
- Restructuring an existing compliance-focused program into a behavior-change program
- Scaling an informal awareness effort into a structured program
- Responding to a regulatory requirement for awareness training
- Post-incident program redesign after a social engineering breach
Input
- Organization: Industry, size, geographic distribution, culture description
- Current state: Existing awareness activities, training history, simulation results
- Budget: Available budget for tools, content, and personnel
- Goals: What the program should achieve (compliance, behavior change, culture change)
- Regulatory requirements: Specific training requirements (HIPAA, PCI-DSS, SOC 2, etc.)
- Risk profile: Top social engineering threats facing the organization
- Constraints: Timeline, technology limitations, language requirements, workforce characteristics
- Champions: Executive sponsor, security team size, department contacts
Process
-
Maturity assessment -- Evaluate current state using the SANS Security Awareness Maturity Model:
- Level 1: Nonexistent (no program)
- Level 2: Compliance-focused (annual training, checkbox)
- Level 3: Promoting awareness and behavior change (engaging, measurable)
- Level 4: Long-term sustainment and culture change (integrated, continuous)
- Level 5: Metrics framework (robust measurement, continuous improvement)
-
Audience segmentation -- Define training tracks based on role and risk:
- All employees: Baseline security awareness
- Executives: BEC, whaling, strategic threats, data protection responsibility
- Finance/accounting: Wire fraud, invoice fraud, payment redirect
- IT/engineering: Supply chain attacks, credential management, secure development
- HR: Data protection, social engineering targeting new hires
- Customer-facing staff: Social engineering via customers, phone scams
- New hires: Onboarding security module
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.
- 2d ago First seen · 163 lines · 0 tokens per session scan A 98e40902d4a3
awareness-plan is a command published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,720 tokens. 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-09-03.
Other commands, from other repositories
explain
Read a BPMN 2.0 .bpmn file and explain it in plain language.
learning-path
Get personalized learning recommendations based on your goals, experience level, and learning style.
ts-glossary
TS bilingual-courseware glossary mode — course terminology glossary.
learn-by-mistake
Briefly summarize recent mistakes and fixes in commonerrors.md, grouped by error category.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.