secrets-management
Skill30 starsChanged 9 months agoApache-2.0View on GitHub
Secure credential handling using environment variables, GitHub secrets, and never committing secrets to source code
- Reads credentials
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 32 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Ensure secure handling of API keys, tokens, and credentials in MCP server development.
- Distinctive: line 90
If a secret is committed:
“Common” is measured: kept by at least 6 in 10 of the 32 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Secrets Management Skill
Purpose
Ensure secure handling of API keys, tokens, and credentials in MCP server development. Zero tolerance for hardcoded secrets.
When to Use
- ✅ Adding external API integrations
- ✅ Configuring CI/CD pipelines with secrets
- ✅ Setting up MCP server authentication
- ✅ Managing GitHub tokens for MCP servers
- ✅ Reviewing code for credential exposure
Golden Rules
Rule 1: Never Commit Secrets
// ❌ NEVER: Hardcoded credentials
const API_KEY = "sk_live_abc123def456";
// ✅ CORRECT: Environment variables
const API_KEY = process.env['EP_API_KEY'] ?? '';Rule 2: Use Environment Variables
// MCP server configuration
const config = {
timeout: Number.parseInt(process.env['EP_REQUEST_TIMEOUT_MS'] ?? '10000'),
baseUrl: process.env['EP_BASE_URL'] ?? 'https://data.europarl.europa.eu/api/v2',
};Rule 3: GitHub Secrets for CI/CD
# .github/workflows/ci.yml
env:
EP_API_KEY: ${{ secrets.EP_API_KEY }}
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}Rule 4: MCP Server Token Security
MCP server tokens are injected at runtime by the GitHub Copilot environment via .github/copilot-mcp.json. Secrets are never stored in configuration files — GitHub resolves ${{ secrets.* }} references during workflow execution:
# .github/copilot-mcp.json uses secret references (resolved by GitHub at runtime)
# The MCP client receives actual token values — never template strings
# See .github/copilot-mcp.json for the canonical configurationEnvironment variables for local development:
export GITHUB_TOKEN="ghp_your_token_here" # Set in shell, never in codeDetection and Prevention
.gitignore Must Include
.env
.env.local
.env.production
*.key
*.pem
secrets/
credentials/Pre-commit Scanning
# GitHub enables secret scanning automatically
# Additional: npm audit, CodeQL analysisIncident Response
If a secret is committed:
- ✅ Rotate the compromised secret immediately
- ✅ Revoke old secret from all systems
- ✅ Review access logs for unauthorized access
- ✅ Clean git history if possible
- ✅ Document incident
ISMS Policy References
Core policies:
- Cryptography Policy — Primary policy: Key lifecycle, approved algorithms, key rotation, secure storage
- Access Control Policy — Secrets access: least privilege, separation of duties, just-in-time
- Secure Development Policy — Never commit secrets, pre-commit scanning, CI secret scanning
- Information Security Policy — Confidentiality is a core security property
Supporting policies:
- Incident Response Plan — Secret-leak incident handling (rotate → revoke → review logs → disclose)
- Segregation of Duties Policy — Separate secret-producer from consumer roles
- Change Management — Rotation as a controlled change
- Open Source Policy — Public-repo hygiene, no secrets in SBOM / artefacts
Other versions34 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 34
- nahid-sparktales/agent-dispatcher★ 59same name
- nimadorostkar/Claude-Skills-collection★ 33same name
- Fandry96/k3-agentic-skills★ 27same name
- xfstudio/skills★ 9same name
- YepAPI/skills★ 8same name
- ai4brands-design/claude-skills★ 2same name
- CodeWithBehnam/cc-docs★ 2same name
- d-o-hub/github-template-ai-agents★ 2same name
- ffsshhttiikk/opencode-agents-skills★ 2same name
- Ghosteken/agent-harness★ 2same name
24 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use background-jobs, input-validation and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
YepAPISkillbackground-jobs
Queue workers with BullMQ/Inngest/Trigger.dev, job retries, dead letter queues, concurrency.
Also in 3 projects that use this
hereshecodesSkillinput-validation
Use when processing user input, form data, file uploads, or query parameters
Also in 3 projects that use this
mattpartidaSkillagent-security
Review and harden OpenClaw/Hermes agent security, including tool permissions, elevated access, exec approvals, allowlists, sandboxing, browser and web exposure, prompt-injection risk, model risk, persistence, and personal-vs-shared trust boundaries. Use when the task is primarily about agent or runtime security rather than host firewall or OS hardening.
Also in 3 projects that use this
harperaaSkillrate-limiting
Implement rate limiting to prevent brute force attacks, spam, and resource abuse. Use this skill when you need to protect endpoints from automated attacks, prevent API abuse, limit request frequency, or control infrastructure costs. Triggers include "rate limiting", "rate limit", "brute force", "prevent spam", "API abuse", "resource exhaustion", "DoS", "withRateLimit", "too many requests", "429 error".
Also in 3 projects that use this
jefflesterSkillapi-security
API security best practices and common vulnerability prevention. Enforces security checks for authentication, input validation, SQL injection, XSS, and OWASP Top 10 vulnerabilities. Use when building or modifying APIs.
Also in 4 projects that use this
MicrosoftSkillsupply-chain-security
Activate when reviewing or modifying dependency resolution, lockfile schema, package downloaders, signature/integrity checks, file integration cleanup, or anything that could expose APM to dependency confusion, typosquatting, malicious packages, or token leakage.
Also in 3 projects that use this
In this repository41 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- ai-development-governanceSkill
- ai-governanceSkill
- architecture-documentationSkill
- aws-security-architectureSkill
- behavioral-analysisSkill
- business-model-canvasSkill
- c4-architecture-documentationSkill
- code-quality-excellenceSkill
- compliance-frameworksSkill
- contribution-guidelinesSkill
- data-science-for-intelligenceSkill
- documentation-standardsSkill
- electoral-analysisSkill
- european-parliament-apiSkill
- european-political-systemSkill
- gdpr-complianceSkill
- github-actions-workflowsSkill
- github-agentic-workflowsSkill
- incident-responseSkill
- intelligence-analysis-techniquesSkill
- isms-complianceSkill
- legislative-monitoringSkill
- mcp-gateway-configurationSkill
- mcp-gateway-securitySkill
- mcp-server-developmentSkill
- open-source-governanceSkill
- osint-methodologiesSkill
- performance-optimizationSkill
- political-science-analysisSkill
- risk-assessment-frameworksSkill
- secure-code-reviewSkill
- secure-development-lifecycleSkill
- security-by-designSkill
- seo-best-practicesSkill
- strategic-communication-analysisSkill
- testing-mcp-toolsSkill
- testing-strategySkill
- threat-modeling-frameworkSkill
- typescript-strict-patternsSkill
- vulnerability-managementSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

