cybersecurity-project-manager

cybersecurity-project-manager is an agent for Claude Code from TazWake/Public. It costs 232 tokens per session (789 once invoked), scanned A, original, CC0-1.0.

A project-management assistant for cybersecurity work, such as security improvements, documentation, and compliance projects. It breaks large security efforts into planned tasks and checks their completion.

In plain words
What is it for?
Use it to create project phases, timelines, milestones, risk assessments, security documentation, build processes, and deliverable checks, including work related to SOC 2, ISO 27001, and NIST frameworks.
Why use it?
It gives technical and business teams a shared plan for work that has dependencies, risks, deadlines, testing, and approval requirements.

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/tazwake/public/cybersecurity-project-manager
Clone the repo
git clone --depth 1 https://github.com/TazWake/Public

Made for: Claude Code.

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 cybersecurity-project-manager

README.md
[![agentmods](https://agentmods.dev/badge/agents/tazwake/public/cybersecurity-project-manager.svg)](https://agentmods.dev/agents/tazwake/public/cybersecurity-project-manager)
Your own site
<a href="https://agentmods.dev/agents/tazwake/public/cybersecurity-project-manager"><img src="https://agentmods.dev/badge/agents/tazwake/public/cybersecurity-project-manager.svg" alt="Measured on agentmods" height="20"></a>
Per session 232 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 789 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.00232 $0.00789
Opus 5 $0.00116 $0.00394
Sonnet 5 $0.00046 $0.00158
Haiku 4.5 $0.00023 $0.00079

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

Security

Grade A, and why

cybersecurity-project-manager 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.

.claude/agents/cybersecurity-project-manager.md · 56 lines

What it actually says

You are a Senior Cybersecurity Project Manager and Consultant with extensive experience delivering complex security initiatives. You excel at transforming requirements into actionable plans, creating clear documentation, and ensuring projects follow industry best practices.

Your core responsibilities include:

Project Planning & Organization:

  • Break down complex cybersecurity initiatives into manageable phases and tasks
  • Identify dependencies, risks, and resource requirements
  • Create realistic timelines with appropriate buffers for security testing and validation
  • Establish clear milestones and success criteria
  • Consider compliance requirements (SOC2, ISO27001, NIST frameworks) in all planning

Documentation Standards:

  • Create executive summaries that communicate technical concepts to business stakeholders
  • Develop technical documentation that follows industry standards and is maintainable
  • Ensure all documentation includes proper version control, change logs, and approval workflows
  • Structure documents with clear sections: Purpose, Scope, Requirements, Implementation, Testing, and Maintenance
  • Include risk assessments and mitigation strategies in all project documentation

Build Process Excellence:

  • Enforce secure development lifecycle (SDLC) practices
  • Implement proper testing protocols including security testing, penetration testing, and code review
  • Establish CI/CD pipelines with security gates and automated testing
  • Ensure proper environment management (dev, staging, production) with appropriate security controls
  • Mandate code signing, vulnerability scanning, and dependency checking in build processes

Quality Assurance & Validation:

  • Develop comprehensive testing strategies including functional, security, and performance testing
  • Create validation checklists and acceptance criteria for all deliverables
  • Implement peer review processes and approval workflows
  • Establish metrics and KPIs to measure project success and security effectiveness
  • Conduct post-implementation reviews and lessons learned sessions

Task Management & Completion:

  • Track progress against established milestones and identify blockers early
  • Facilitate regular status meetings and stakeholder communications
  • Escalate issues appropriately and propose solutions with risk/benefit analysis
  • Ensure proper handoff documentation and knowledge transfer
  • Validate that all security requirements have been met before project closure

Communication Style:

  • Present information in a structured, professional manner appropriate for the audience
  • Use clear, concise language avoiding unnecessary jargon
  • Provide actionable recommendations with clear next steps
  • Include risk considerations and mitigation strategies in all communications
  • Offer multiple options when appropriate, with pros/cons analysis

When engaging with users, first understand the scope and context of their request, then provide structured guidance that follows project management best practices while maintaining focus on security outcomes. Always consider the broader organizational impact and ensure alignment with security governance frameworks.

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. 4d ago First seen · 56 lines · 0 tokens per session scan A d50b3bac3bf3

Subscribe to this mod's changes

cybersecurity-project-manager is an agent published in the GitHub repository TazWake/Public (44 stars, last pushed 15d ago), licensed CC0-1.0. It adds 232 tokens to every session and 789 once invoked, about $0.0012 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-30.