Works with the AI Agents you already use
Data Secrets Crypto Review
Review secrets, PII and cryptographic boundaries across the full data lifecycle
$17
Data Secrets Crypto Review
Example session with this skill installed
Review this synthetic application's handling of API credentials, customer PII, password storage, logs, encryption, retention, and deletion. Identify supported data or secret exposure risks and inappropriate cryptographic choices. Do not retrieve secret values or modify the project.
- Read your context and instructions
- Compiled the data secrets crypto
Illustrative synthetic demo. It demonstrates the expected review structure. No production repository, real credential, customer record, external service, or live secret store was accessed.
Data, Secrets and Crypto Review Record
SCOPE
Synthetic web application containing authentication code, logging configuration, customer profile storage, and secret references.
Sensitive Data Inventory
| Data class | Example handling | Review status |
|---|---|---|
| Customer email | Database and application logs | REVIEWED |
| Password | Password hashing path | REVIEWED |
| API credential | Environment reference | REVIEWED WITHOUT VALUE ACCESS |
| Session token | Authentication flow | PARTIALLY REVIEWED |
| Customer export | Export handler | REVIEWED |
Finding DSC-01
Area
Sensitive data logging
Synthetic observation
The illustrative request logger records the full customer profile object after an account update.
The modeled object includes an email address and internal customer identifier.
Exposure
SUPPORTED IN SYNTHETIC EXAMPLE
Sensitive fields are sent to application logging without a redaction boundary.
Recommended control
Define an explicit logging allowlist or structured redaction policy before customer objects reach the logging sink.
Finding DSC-02
Area
Password storage
Synthetic observation
The worked example uses an established password hashing function with a per password salt.
Assessment
NO DEFECT SUPPORTED IN SYNTHETIC EXAMPLE
No plaintext password persistence or reversible encryption path is present in the supplied synthetic surface.
Finding DSC-03
Area
Application secret handling
Synthetic observation
The application references an API credential through an environment variable name.
The value itself is not inspected.
Assessment
NO SECRET VALUE OBSERVED
The presence of a secret reference does not establish that the secret has leaked.
Finding DSC-04
Area
Retention and deletion
Synthetic observation
The primary customer record is deleted, but the supplied synthetic implementation does not establish whether generated exports or historical backups follow the same deletion lifecycle.
Status
UNVERIFIED
Recommended next step
Document the retention and deletion policy for exports and backups before claiming complete deletion coverage.
Crypto Property Review
Password confidentiality
Handled through password hashing in the synthetic example.
Transport confidentiality
UNVERIFIED. Runtime TLS configuration was not supplied.
Application data encryption at rest
UNVERIFIED. Storage platform evidence was not supplied.
Custom cryptography
NONE OBSERVED in the supplied synthetic scope.
Review Boundary
No environment variable value was read.
No credential was displayed.
No production key was generated.
No external secret store was contacted.
No claim of a real data breach is made.
Priority Summary
- Prevent customer PII from entering application logs.
- Establish retention and deletion coverage for exports and backups.
- Obtain runtime and storage evidence before making transport or at rest encryption claims.
Connects securely to your tools. The creator never sees your data.
About this skill
Reviews how sensitive data, application secrets, cryptographic keys, and protected information move through an application from collection to deletion. It evaluates whether each security property is enforced with the appropriate control without inventing cryptographic requirements or treating unverified scanner signals as confirmed exposure.
What it does
- Maps sensitive data, secrets, credentials, keys, tokens, and protected identifiers across the application lifecycle.
- Reviews secret handling and key boundaries without exposing secret values.
- Evaluates cryptographic primitive selection against the property the system actually needs.
- Reviews encryption at rest and in transit where relevant.
- Checks logging, telemetry, tracing, and error handling for accidental sensitive data exposure.
- Reviews redaction and masking behavior.
- Examines storage, retention, backup, export, and deletion paths.
- Distinguishes confirmed exposure from hypothetical risk and missing evidence.
- Identifies custom or inappropriate cryptographic patterns that should be replaced by established primitives.
How it works
- Data inventory identifies sensitive data classes and the components that handle them.
- Lifecycle mapping follows each class through collection, processing, storage, transmission, logging, retention, and deletion.
- Secret boundary review checks where credentials, API keys, signing keys, tokens, and other secrets originate and where they are permitted to exist.
- Cryptographic review maps confidentiality, integrity, authenticity, password storage, and key management requirements to appropriate primitive classes.
- Exposure review examines logs, errors, telemetry, source files, configuration, and persistence paths for unnecessary disclosure.
- Findings separate observed evidence, supported inference, and unresolved gaps before recommending the appropriate remediation workflow.
Boundaries
This skill focuses on sensitive data, secret handling, and cryptographic design.
General application vulnerability review belongs to secure-code-review. Authentication and authorization architecture belongs to identity-access-review. Runtime and deployment configuration belongs to security-config-review.
The skill does not retrieve or display real secret values, rotate credentials, generate production keys, invent custom cryptographic protocols, or claim a breach based only on a scanner match.
Why this beats prompting it yourself
Generic security prompts often search for strings that resemble secrets and stop there. They may also recommend encryption without identifying what security property is required or suggest custom cryptographic constructions without considering lifecycle and key boundaries. This skill reviews the full sensitive data path and maps each property to the appropriate control before classifying risk.
Validation
At pack level, JetFerrari Security Engineering passed 58/58 routing integrity checks with zero unresolved cases.
Routing boundary stress testing for this skill also covered 5 targeted high risk negative cases. All 5 correctly kept this skill inactive when another workflow was the appropriate route, with zero false triggers.
Use cases
- Review how application secrets and cryptographic keys are handled.
- Identify sensitive data leaking into logs or telemetry.
- Review encryption and key boundaries for protected data.
- Assess PII retention, export, and deletion behavior.
- Review password, token, signing, hashing, and encryption primitive choices.
- Separate credible secret exposure from scanner noise.
Known limitations
The review depends on the source code, configuration, architecture, logging behavior, storage design, key management context, and data lifecycle information available to the agent. Missing runtime, storage, or operational evidence remains UNVERIFIED. The skill does not access secret values from environment variables by default, rotate credentials, generate production keys, or independently prove that a suspected exposure resulted in a real breach.
Part of JetFerrari Security Engineering.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Security.
The review depends on the source code, configuration, architecture, logging behavior, storage design, key management context, and data lifecycle information available to the agent. Missing runtime, storage, backup, or operational evidence remains UNVERIFIED. The skill does not access secret values from environment variables by default, rotate credentials, generate production keys, or independently prove that a suspected exposure resulted in a real breach.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 24 days ago
Permissions
Access is limited to source code, configuration, logging behavior, data flows, and security context supplied for the review. The skill may inspect references to secrets and environment variables but does not require or retrieve their values. It does not modify files, rotate credentials, generate production keys, contact external secret stores, or expose sensitive values.