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 skills add HoangNguyen0403/agent-skills-standard --skill cyber-purple-validationgit clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standardWrote 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/skills/hoangnguyen0403/agent-skills-standard/cyber-purple-validation)<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/cyber-purple-validation"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/cyber-purple-validation/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.
<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/cyber-purple-validation"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/cyber-purple-validation.svg" alt="Reviewed on agentmods" width="80" 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.00025 | $0.00831 |
| Opus 5.5 | $0.00010 | $0.00332 |
| Sonnet 5.5 | $0.00005 | $0.00166 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
cyber-purple-validation 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 yesterday.
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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cyber Purple Validation Skill
[!IMPORTANT] Controlled purple validation using paired action-observation evidence, explicit defensive outcomes, and optional isolated lab routing.
Optional args: slug=, ticket=<id/url>, mode=interactive|autonomous|channel, channel=, auto_continue=true|false, profile=business|hybrid|technical.
Instructions
When the user asks to perform this workflow, execute the following steps:
Cyber Purple Validation
Goal: Validate detection and defense controls using paired action-observation evidence across replay, offline analysis, or isolated lab validation.
Runtime Contract
Compose cyber-detection-validation, cyber-authorization, cyber-evidence, cyber-framework-mapping, and optionally cyber-lab-validation. Controlled synthetic/offline fixtures only. Active operations require documented scope, approved action, accountable owner, and runtime-proven controls. No Markdown claim is enforcement or production efficacy.
Steps
- Hypothesis and Mode: Define control hypothesis, entity, time window, expected observation, and stop condition. Classify step mode as
analysis,replay,isolated-lab-validation, ordefensive-verification. - Authorize and Gate: Obtain action-specific authorization and verify host runtime controls before active steps. If unauthorized or unsupported, record step
blockedwith reason; do not simulate success. - Execute or Route:
- For
analysis: inspect detection logic, queries, and configs offline. - For
replay: replay synthetic telemetry through pipeline; report only stages actually exercised (e.g. parser, correlation), not sensor efficacy or prevention unless evidenced. - For
isolated-lab-validation: loadcyber-lab-validationon disposable synthetic fixtures under verified host containment.
- For
- Isolate and Continue: If an active step is blocked or refused, mark dependent verification
dependency-blocked(evidence-missing). Continue independent rule tuning, detection logic, and remediation. Never fabricate evidence. - Capture Paired Evidence: Link action receipt and observation record by
(run_id, attempt_id, test_id), entity, time window, and source. - Classify Outcome: Classify defensive outcome strictly from paired evidence:
blocked,prevented,detected,responded, ortelemetry-gap. An action without observation istelemetry-gap; blocked execution isblocked(never prevented). - Document Findings: Record finding status, evidence references, limitations, cleanup result, and accountable owner. Use
artifacts/security-review.mdwhen security-review material.
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.
- yesterday Changed · +6 lines · +6 tokens per session 57c865f61778
- 28d ago Changed · +1 lines abdbf9e35d27
- 1mo ago First seen · 60 lines · 19 tokens per session scan A 4aca45f6a01a
cyber-purple-validation is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (582 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 831 once invoked, about $0.0001 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-24.
Other skills, from other repositories
browser-automation
Playwright browser automation via MCP. Covers E2E testing, UI review, web scraping, screenshot capture, and general browser interaction. MCP-first — CLI is fallback only.
vue-idioms
Vue 3 Composition API patterns: syntax, reactive state with Pinia stores, reusable composables, and Vitest component testing. Use when developing or refactoring Vue 3 frontend applications.
python-idioms
Modern Python (3.11+) idioms: type annotations, typing Protocols, Pydantic models, asyncio, pytest fixtures, and Ruff/Mypy strict compliance. Use when writing, refactoring, or reviewing Python applications, APIs, or scripts.
testability-patterns
Implementation examples for the three testability rules (I/O isolation, pure logic, dependency direction) across Go, TypeScript, Python, Rust, and Dart. Loaded by reference from architectural-pattern.md — not triggered by file patterns.
testing-strategy
Detailed testing reference material: test doubles strategy, integration test infrastructure (Testcontainers, Firebase emulator), naming conventions per language, test organization patterns. Load when writing tests or setting up test infrastructure. The core mandates (TDD, AAA, pyramid) are in the testing-strategy rule…
react-testing
React testing guidance using React Testing Library and modern patterns.