14 factor security privacy
Skill Just-Agent/just-product-factor/skills/14-factor-security-privacy
Reusable Factor Skills for Agent-native product optimization
npx -y skills add Just-Agent/just-product-factor --skill 14-factor-security-privacyAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
4.1 KB, as published. Nobody here has run it
14-factor-security-privacy Skill
Version: v0.8.0
Skill name
14-factor-security-privacy
Purpose
Use 14-factor-security-privacy to audit and improve security, privacy, secrets, permission boundaries, dependency hygiene, data handling, and release safety for product engineering repositories. It is designed as a practical product-readiness layer, not a heavy compliance program.
When to use
Use this Skill when:
- A project handles user data, API keys, credentials, uploaded files, tokens, logs, model outputs, or third-party integrations.
- A repository is moving from demo to public release and needs a security/privacy pass.
- A product includes Agent tools, MCP tools, RAG pipelines, CI/CD workflows, web apps, CLIs, or hosted services.
- A user asks whether the project is safe to publish, deploy, share, or open source.
- Another Factor Skill finds issues around permissions, logs, supply chain, secrets, or data retention.
When not to use
Do not use this Skill as legal advice, formal compliance certification, penetration testing, or a replacement for organization-specific security review. For regulated domains, use it as a preparation checklist before specialist review.
Inputs
Inspect README, configuration files, environment variable docs, .gitignore, examples, logs, workflows, package manifests, lockfiles, Docker files, deployment docs, API/tool schemas, auth code, storage paths, data examples, and release notes.
Workflow
- Identify what data, credentials, files, tokens, and permissions the project touches.
- Map trust boundaries across users, Agent, tools, workflows, storage, network calls, and third-party services.
- Check repository hygiene: secrets, fixtures, generated artifacts, logs, ignored files, and sample configs.
- Review dependency, workflow, and release risks.
- Score with
scoring-rubric.md. - Produce an audit report using
audit-report-template.md. - Produce a prioritized mitigation plan using
refactor-plan-template.md. - Pair with a domain Skill such as
12-factor-agents,12-factor-app,7-factor-mcp,8-factor-github-actions, or9-factor-ragwhen technical depth is required.
Fourteen factors
- Asset Inventory — Data, credentials, files, and privileged operations are identified.
- Secret Hygiene — Real secrets are not committed, logged, or embedded in examples.
- Configuration Safety —
.env.example, defaults, and docs avoid unsafe production settings. - Permission Boundaries — Tools, tokens, workflows, and APIs use least privilege.
- Input Validation — User, model, file, URL, and tool inputs are validated before use.
- Output and Log Safety — Logs, reports, traces, and examples avoid sensitive leakage.
- Data Handling — Retention, deletion, anonymization, and storage expectations are documented.
- Dependency Hygiene — Dependencies, lockfiles, and supply-chain risks are visible and updatable.
- CI/CD Security — Workflows avoid overbroad tokens, unsafe pull request execution, and secret exposure.
- Agent and Tool Safety — Agent tool calls have clear contracts, guardrails, and failure handling.
- MCP and Integration Safety — External tools and MCP servers document schemas, permissions, and trust limits.
- RAG and Knowledge Safety — Retrieval pipelines avoid leaking private data and track source boundaries.
- Release and Disclosure Readiness — Security notes, support contact, and vulnerability reporting are present.
- Validation Evidence — The project includes lightweight checks or manual evidence for high-risk areas.
Scoring
Use scoring-rubric.md. Score each factor from 0 to 5, then convert to a 100-point readiness score.
Output format
Return:
- Security/privacy scope summary.
- Trust boundary map.
- 14-factor scorecard.
- Critical release blockers.
- Secrets and data-handling findings.
- CI/CD, dependency, and tool-permission findings.
- Prioritized mitigation plan.
- Validation results or validation limits.
- Recommended paired Skills.
Example calls
See usage-examples.md.
Version record
v0.8.0: Added as a first-class security/privacy readiness Skill.