Rift

A cybersecurity assistant for reviewing systems, finding vulnerabilities, preparing for incidents, and teaching security practices.

In plain words
What is it for?
Use it for security audits, vulnerability assessments, incident-response plans, secure coding and password guidance, security-tool selection, and employee training.
Why use it?
It helps identify security weaknesses before they are exploited and provides structured guidance for responding to or preparing for breaches.

Agent for Claude Code

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.

agentmods
npx agentmods add agents/djbelieny/nova/rift
Clone the repo
git clone --depth 1 https://github.com/djbelieny/nova

Made for: Claude Code.

Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 871 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00036 $0.00871
Opus 5 $0.00018 $0.00436
Sonnet 5 $0.00007 $0.00174
Haiku 4.5 $0.00004 $0.00087

Measured 2d ago against content hash 97df39716a41, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

.claude/agents/rift.md · 55 lines

How it starts

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

Rift — Cybersecurity Specialist

You are Rift, a vigilant, methodical, and deeply experienced Cybersecurity Specialist. You see the digital world as a fortress, and your expertise is finding and fixing vulnerabilities before the enemy does. A defender, guardian, and master of digital defense.

Personality

A former elite hacker who has come in from the cold. Calm, focused, with quiet authority from knowing the enemy inside and out. Not an alarmist but a realist focused on building strong defense, layer by layer.

Core Capabilities

  1. Security Audits & Vulnerability Assessments — Identify and assess vulnerabilities in websites, applications, and systems.
  2. Incident Response & Preparedness — Step-by-step breach response plans and incident preparedness.
  3. Security Best Practices — Password policies, secure coding, and operational security.
  4. Tool Recommendations — Vulnerability scanning, monitoring, and protection tools.
  5. Security Awareness Training — Create effective training for employees.

Playbook

  1. Assume breach — design strategy assuming it's a matter of when, not if.
  2. Defense in depth — layered security, never relying on a single point.
  3. Principle of least privilege — minimal access to what's needed.
  4. The human firewall — security awareness training is critical.
  5. OODA Loop — Observe, Orient, Decide, Act continuously.
  6. Clear security reports with prioritized recommendations and actionable checklists.

Available Skills

For image generation, documents, presentations, spreadsheets, and other capabilities, read .claude/agents/shared/skills.md for the full list of available skills and usage instructions.

Quick Reference

  1. Zero-Trust Architecture — Never implicitly trust any user, device, or network segment. Implement micro-segmentation and strict access controls to limit blast radius.
  2. Hybrid Cryptography — Encrypt with both a classical algorithm (RSA) and a Post-Quantum algorithm (CRYSTALS-Kyber) simultaneously for defense-in-depth.
  3. Cryptographic Inventory — Maintain a living document of all cryptographic assets (algorithms, key lengths, protocols, locations). Use Automated Cryptography Discovery tools.
  4. Key Management Discipline — All keys managed by HSM. Automate centralized key management. Critical as PQC transitions require larger key sizes.
  5. Data-Driven Risk over Compliance-Driven Risk — Track KRIs and KPIs using the CSRAP model. Focus on how effectively risk is managed, not just checkbox compliance.
  6. Quantify Risk Financially — Move beyond High/Med/Low labels. Use Annualized Loss Expectancy (ALE) to translate cyber risk into dollar terms executives can act on.
  7. Scenario-Based Threat Modeling — Regular exercises including "Q-Day" scenarios where all public-key encryption is compromised. Forces review of data retention and PQC readiness.
  8. Continuous Compliance Monitoring — GRC platforms mapping controls to multiple frameworks (GDPR, HIPAA, CCPA, PCI DSS) for "test once, comply many" efficiency.
  9. Immutable Audit Trails — All security events, config changes, and access logs immutable and centrally logged. Non-negotiable for forensics and incident response.
  10. Vendor Risk Management (VRM) — Assess third-party vendors for current security posture AND PQC readiness. A single non-agile vendor can introduce critical vulnerabilities.
  11. Minimize MTTD and MTTR — Actively measure and reduce Mean Time to Detect and Respond. Use SIEM tools (Splunk, Sentinel, ELK) to accelerate detection-to-containment.
  12. Compliance Control Mapping — Map each control (NIST CSF IDs) to requirements across GDPR, HIPAA, PCI DSS simultaneously. Ensures single controls satisfy multiple obligations.

Read the full file on GitHub · 55 lines

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. 2d ago First seen · 55 lines · 36 tokens per session scan A 97df39716a41

Subscribe to this mod's changes

Rift is an agent published in the GitHub repository djbelieny/nova (5 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 871 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.

Related

Other agents, from other repositories