.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/cyberstrikeus/cyberstrike
home/skills/cyberstrikeus/cyberstrike
cyberstrikeus avatar

cyberstrikeus/cyberstrike

60 skills

View on GitHub
$npx skills add cyberstrikeus/cyberstrike
SkillInstalls
cis-aws-compute-10.1Ensure Managed Platform updates is configured—cis-aws-compute-10.2Ensure Persistent logs is setup and configured to S3—cis-aws-compute-10.3Ensure access logs are enabled—cis-aws-compute-10.4Ensure that HTTPS is enabled on load balancer—cis-aws-compute-11.1Ensure customer-managed keys are used to encrypt AWS Fargate ephemeral storage data for Amazon ECS—cis-aws-compute-12.1Ensure AWS Config is Enabled for Lambda and Serverless—cis-aws-compute-12.10Ensure Lambda functions do not allow unknown cross account access via permission policies—cis-aws-compute-12.11Ensure that the runtime environment versions used for your Lambda functions do not have end of support dates—cis-aws-compute-12.12Ensure encryption in transit is enabled for Lambda environment variables—cis-aws-compute-12.2Ensure Cloudwatch Lambda insights is enabled—cis-aws-compute-12.3Ensure AWS Secrets manager is configured and being used by Lambda for databases—cis-aws-compute-12.4Ensure least privilege is used with Lambda function access—cis-aws-compute-12.5Ensure every Lambda function has its own IAM Role—cis-aws-compute-12.6Ensure Lambda functions are not exposed to everyone—cis-aws-compute-12.7Ensure Lambda functions are referencing active execution roles—cis-aws-compute-12.8Ensure that Code Signing is enabled for Lambda functions—cis-aws-compute-12.9Ensure there are no Lambda functions with admin privileges within your AWS account—cis-aws-compute-16.1Ensure communications between your applications and clients is encrypted—cis-aws-compute-2.1.1Ensure Consistent Naming Convention is used for Organizational AMI—cis-aws-compute-2.1.2Ensure Amazon Machine Images (AMIs) are encrypted—cis-aws-compute-2.1.3Ensure Only Approved Amazon Machine Images (AMIs) are Used—cis-aws-compute-2.1.4Ensure Images (AMI) are not older than 90 days—cis-aws-compute-2.1.5Ensure Images are not Publicly Available—cis-aws-compute-2.10Ensure unused ENIs are removed—cis-aws-compute-2.11Ensure instances stopped for over 90 days are removed—cis-aws-compute-2.12Ensure EBS volumes attached to an EC2 instance are marked for deletion upon instance termination—cis-aws-compute-2.13Ensure Secrets and Sensitive Data are not stored directly in EC2 User Data—cis-aws-compute-2.14Ensure EC2 Auto Scaling Groups Propagate Tags to EC2 Instances that it launches—cis-aws-compute-2.2.1Ensure EBS volume encryption is enabled—cis-aws-compute-2.2.2Ensure Public Access to EBS Snapshots is Disabled—cis-aws-compute-2.2.3Ensure EBS volume snapshots are encrypted—cis-aws-compute-2.2.4Ensure unused EBS volumes are removed—cis-aws-compute-2.3Ensure Tag Policies are Enabled—cis-aws-compute-2.4Ensure an Organizational EC2 Tag Policy has been Created—cis-aws-compute-2.5Ensure no AWS EC2 Instances are Older than 180 days—cis-aws-compute-2.6Ensure detailed monitoring is enabled for production EC2 Instances—cis-aws-compute-2.7Ensure Default EC2 Security groups are not being used—cis-aws-compute-2.8Ensure the Use of IMDSv2 is Enforced on All Existing Instances—cis-aws-compute-2.9Ensure use of AWS Systems Manager to manage EC2 instances—cis-aws-compute-3.1Ensure Amazon ECS task definitions using 'host' network mode do not allow privileged or root user access to the host—cis-aws-compute-3.10Ensure Amazon ECS services are tagged—cis-aws-compute-3.11Ensure Amazon ECS clusters are tagged—cis-aws-compute-3.12Ensure Amazon ECS task definitions are tagged—cis-aws-compute-3.13Ensure only trusted images are used with Amazon ECS—cis-aws-compute-3.14Ensure 'assignPublicIp' is set to 'DISABLED' for Amazon ECS task sets—cis-aws-compute-3.2Ensure 'assignPublicIp' is set to 'DISABLED' for Amazon ECS services—cis-aws-compute-3.3Ensure Amazon ECS task definitions do not have 'pidMode' set to 'host'—cis-aws-compute-3.4Ensure Amazon ECS task definitions do not have 'privileged' set to 'true'—cis-aws-compute-3.5Ensure 'readonlyRootFilesystem' is set to 'true' for Amazon ECS task definitions—cis-aws-compute-3.6Ensure secrets are not passed as container environment variables in Amazon ECS task definitions—cis-aws-compute-3.7Ensure logging is configured for Amazon ECS task definitions—cis-aws-compute-3.8Ensure Amazon ECS Fargate services are using the latest Fargate platform version—cis-aws-compute-3.9Ensure monitoring is enabled for Amazon ECS clusters—cis-aws-compute-5.1Apply updates to any apps running in Lightsail—cis-aws-compute-5.10Enable storage bucket access logging—cis-aws-compute-5.11Ensure your Windows Server based lightsail instances are updated with the latest security patches—cis-aws-compute-5.12Change the auto-generated password for Windows based instances—cis-aws-compute-5.2Change default Administrator login names and passwords for applications—cis-aws-compute-5.3Disable SSH and RDP ports for Lightsail instances when not needed—cis-aws-compute-5.4Ensure SSH is restricted to only IP address that should have this access—