What is phoenix-security-engineer?

A threat-modelling step that examines how Phoenix data and services cross trust boundaries and turns the findings into security requirements. Threat modelling is the practice of identifying ways systems or data could be attacked.

Use it to assess Phoenix trust boundaries and protect assets such as API keys, software bills of materials, reachability results, vulnerability data, and AI inputs and outputs.

It helps uncover risks involving customer tenants, connected security tools, CI/CD systems, cloud services, credentials, vulnerability data, and AI models before implementation.

phoenix-security-engineer — Skill by Security-Phoenix-demo

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 Security-Phoenix-demo/security-skills-claude-code --skill phoenix-security-engineer

Clone the repo

git clone --depth 1 https://github.com/Security-Phoenix-demo/security-skills-claude-code

Made for: Claude Code.

Or install phoenix-prd-pipeline, the plugin that ships this one along with the rest of its 13 skills.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/security-phoenix-demo/security-skills-claude-code/phoenix-security-engineer/github.svg)](https://agentmods.dev/skills/security-phoenix-demo/security-skills-claude-code/phoenix-security-engineer)

Your own site

<a href="https://agentmods.dev/skills/security-phoenix-demo/security-skills-claude-code/phoenix-security-engineer"><img src="https://agentmods.dev/badge/skills/security-phoenix-demo/security-skills-claude-code/phoenix-security-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/security-phoenix-demo/security-skills-claude-code/phoenix-security-engineer"><img src="https://agentmods.dev/badge/skills/security-phoenix-demo/security-skills-claude-code/phoenix-security-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 197 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,151 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.

Model	Per session	Once invoked
Fable 5.1	$0.00197	$0.01151
Opus 5.5	$0.00079	$0.00460
Sonnet 5.5	$0.00039	$0.00230
Haiku 4.5	$0.00020	$0.00115

Measured 1mo ago against content hash 229c54eaf019, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

phoenix-security-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 1mo 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.

plugins/phoenix-prd-pipeline/skills/phoenix-security-engineer/SKILL.md · 105 lines

How it starts

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

Phoenix Security — Security Engineer (Role 06)

Token Budget: ≤1200 tokens Depends On: Roles 01–04 — CLEAN_CONTEXT, SCOPE_DEFINITION, ACTIVE_SET, NORMATIVE_REQUIREMENTS Feeds Into: Role 07 — Contract Architect Output: 06-security.md

Phoenix Trust Boundaries (evaluate all; include applicable ones in threat model)

Customer tenant ↔ Phoenix platform — vuln data, asset inventory, API keys (strongest boundary)
Phoenix platform ↔ integrated tools — GitHub AS, Snyk, Qualys, Wiz, Azure SC, Backstage, Jenkins
Phoenix platform ↔ AI/LLM layer — GCP Gemini custom model, Claude API — prompt/response handling
Phoenix platform ↔ customer CI/CD — Jenkins/GitHub Actions gating; code execution adjacency
Phoenix platform ↔ AWS infra — onboarding, core services, secrets management
Phoenix CTI ↔ GCP — vuln scanning, CTI enrichment, CISA KEV correlation

High-Value Assets (address applicable ones)

Customer vulnerability data (CONFIDENTIAL)
API keys / integration credentials (per-tenant)
Reachability analysis results (code structure exposure)
SBOM / dependency graph data
AI model inputs/outputs (prompt injection surface)
Board-level risk reports (exec-grade, NDA)

Phoenix AI Agent Security Posture

Agents MUST be assistive-only, disabled by default
No autonomous action without explicit user confirmation
No customer data ingestion by AI without opt-in
Prompt injection is P0 for any LLM-touching feature
Attribution + prioritisation must complete before any agent action

Regulatory Context

UK: NCSC Cyber Essentials, UK GDPR, DORA (financial sector)
US: NIST CSF, FedRAMP-awareness, CISA KEV compliance

Core Rules

No fictional threats — ground every control in actual feature behaviour and data flows.
Every security MUST must be verifiable (test/contract/static/manual).
Preventative first, detective second, corrective third.
Prompt injection is a required threat entry if any LLM component is in scope.
PSC-03 (multi-tenancy) must appear in threat model whenever customer data flows exist.
MITRE ATT&CK: map high-risk flows to techniques where applicable.

Read the full file on GitHub · 105 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.

1mo ago First seen · 105 lines · 197 tokens per session scan A 229c54eaf019

Subscribe to this mod's changes

phoenix-security-engineer is a skill published in the GitHub repository Security-Phoenix-demo/security-skills-claude-code (81 stars, last pushed 5d ago), licensed MIT. It adds 197 tokens to every session and 1,151 once invoked, about $0.0008 per session on Opus 5.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-09-11.