Layerkit Privacy Review
Review and update client-owned privacy, consent, hashing, redaction, and egress checks before vendor integration changes ship.
Install
$ agentstack add skill-hariharapanigrahy-layerkit-layerkit-privacy-review ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-hariharapanigrahy-layerkit-layerkit-privacy-review) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
layerkit-privacy-review
Privacy review is source-code review plus evidence capture. Layerkit does not provide a runtime privacy gate for the client package.
Protocol
- Inventory new or changed fields from the vendor contract and client mapper.
- Classify likely PII/regulated data from field meaning, customer code, and policy evidence.
- Inspect existing consent, hashing, redaction, allowlist, denylist, and region checks in the client package.
- Update existing privacy code/tests directly when the vendor change requires it.
- Move raw API keys, passwords, private keys, bearer tokens, and credentials to environment variables or the client's secrets manager. In public or shared repos, source string literals that contain secrets are release blockers. Do not paste them into Layerkit memory/proposals/tests.
- Leave a TODO only when customer policy or datalayer support is missing.
- Record a redacted memory note:
layerkit memory append --type privacy --title "privacy review " --vendor --body-file ./privacy-digest.md- Run the client package tests that cover privacy behavior and
layerkit doctor.
Forbidden
- Inventing legal basis, consent meaning, or privacy classification.
- Pasting real PII into Layerkit memory, proposals, tests, or docs.
- Leaving API keys, passwords, or tokens as source string literals.
- Shipping public/shared code while secret-like literals remain in source.
- Adding a parallel privacy layer when the existing client privacy path can be changed.
- Treating a Layerkit proposal as production privacy enforcement.
- Self-approving a privacy-sensitive change in strict maker-checker mode.
Success Criteria
- [ ] Changed PII fields are covered by existing or updated client checks.
- [ ] Privacy tests were updated when behavior changed.
- [ ] Secret-like values are env/SecretRef/secrets-manager references, not literals.
- [ ] Digest names residual human questions without raw PII.
- [ ] Unsupported data/policy gaps are explicit TODOs in the integration path.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: hariharapanigrahy
- Source: hariharapanigrahy/layerkit
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.