Cloud Audit
briiirussell/cybersecurity-skills
Audit cloud infrastructure (AWS, GCP, Azure) for misconfigurations, excessive permissions, and security gaps.
Diagnoses and resolves Amazon EFS issues including mount failures, NFS timeouts, permission errors, throughput problems, and burst credit exhaustion.
Install Troubleshooting Efs
$ npx skills add aws/agent-toolkit-for-aws --skill troubleshooting-efs -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aws/agent-toolkit-for-aws troubleshooting-efs --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/specialized-skills/storage-skills/troubleshooting-efs .claude/skills/troubleshooting-efs && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "troubleshooting-efs" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/storage-skills/troubleshooting-efs into .claude/skills/troubleshooting-efs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshooting-efs", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/storage-skills/troubleshooting-efsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add aws/agent-toolkit-for-aws --skill troubleshooting-efs -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aws/agent-toolkit-for-aws troubleshooting-efs --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/specialized-skills/storage-skills/troubleshooting-efs .agents/skills/troubleshooting-efs && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "troubleshooting-efs" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/storage-skills/troubleshooting-efs into .agents/skills/troubleshooting-efs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshooting-efs", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aws/agent-toolkit-for-aws --skill troubleshooting-efs -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aws/agent-toolkit-for-aws troubleshooting-efs --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/specialized-skills/storage-skills/troubleshooting-efs .cursor/skills/troubleshooting-efs && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "troubleshooting-efs" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/storage-skills/troubleshooting-efs into .cursor/skills/troubleshooting-efs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshooting-efs", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/aws/agent-toolkit-for-aws.git --path skills/specialized-skills/storage-skills/troubleshooting-efs--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add aws/agent-toolkit-for-aws --skill troubleshooting-efs -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aws/agent-toolkit-for-aws troubleshooting-efs --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/specialized-skills/storage-skills/troubleshooting-efs .gemini/skills/troubleshooting-efs && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "troubleshooting-efs" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/storage-skills/troubleshooting-efs into .gemini/skills/troubleshooting-efs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshooting-efs", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install aws/agent-toolkit-for-aws troubleshooting-efsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add aws/agent-toolkit-for-aws --skill troubleshooting-efs -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/specialized-skills/storage-skills/troubleshooting-efs .github/skills/troubleshooting-efs && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "troubleshooting-efs" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/storage-skills/troubleshooting-efs into .github/skills/troubleshooting-efs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshooting-efs", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aws/agent-toolkit-for-aws --skill troubleshooting-efs -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aws/agent-toolkit-for-aws troubleshooting-efs --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aws/agent-toolkit-for-aws.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/specialized-skills/storage-skills/troubleshooting-efs .opencode/skills/troubleshooting-efs && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "troubleshooting-efs" agent skill from https://github.com/aws/agent-toolkit-for-aws/tree/main/skills/specialized-skills/storage-skills/troubleshooting-efs into .opencode/skills/troubleshooting-efs/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshooting-efs", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
troubleshooting-efs- GitHub stars
- 2.8k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 618 words
- Files
- 1
- Skills in repo
- 138
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Diagnoses and resolves Amazon EFS issues including mount failures, NFS timeouts, permission errors, throughput problems, and burst credit exhaustion.
- Works in 8 steps: Verify Dependencies → Classify the Issue → Category A — Missing NFS Client → …
- The user has an EFS file system that is not mounting
- SKILL.md covers Overview, Common Tasks, Troubleshooting and Security Considerations, plus 1 more section
- Calls aws, yum and apt-get
What it does
Troubleshooting Efs is an agent skill from aws/agent-toolkit-for-aws, published by the product's own GitHub organization. Diagnoses and resolves Amazon EFS issues including mount failures, NFS timeouts, permission errors, throughput problems, and burst credit exhaustion. Use when the user has an EFS file system that is not mounting, returning errors, performing slowly, or showing access denied.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Security. It works with Amazon Web Services. The repository describes itself as: Official, AWS-supported MCP servers, skills, and plugins to help AI agents build on AWS. The licence is Apache-2.0.
When your agent uses it
- The user has an EFS file system that is not mounting
- Returning errors
- Performing slowly
- Showing access denied
Example prompts
- “Use the troubleshooting-efs skill to diagnose and resolves Amazon EFS issues including mount failures, NFS timeouts, permission errors, throughput…”
- “/troubleshooting-efs”
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit df2ab44. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
awsyumapt-get
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
docs.aws.amazon.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Troubleshooting Efs loads about 1.6k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 618 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteRuns commands with sudoSKILL.md:48
sudo yum -y install amazon-efs-utils # preferred (includes mount helper + TLS) - NoteRuns commands with sudoSKILL.md:50
sudo yum -y install nfs-utils - NoteRuns commands with sudoSKILL.md:53
sudo apt-get install nfs-common - NoteRuns commands with sudoSKILL.md:164
sudo tar -czf /tmp/efs-logs.tar.gz /var/log/amazon/efs/ /etc/amazon/efs/efs-utils.conf
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from aws/agent-toolkit-for-aws at commit df2ab44, republished under its Apache-2.0 licence (© aws). 618 words, ~1,617 tokens.
Download SKILL.mdSave it as
.claude/skills/troubleshooting-efs/SKILL.md (or your agent's skills folder).- name
- troubleshooting-efs
- description
- Diagnoses and resolves Amazon EFS issues including mount failures, NFS timeouts, permission errors, throughput problems, and burst credit exhaustion. Use when the user has an EFS file system that is not mounting, returning errors, performing slowly, or showing access denied.
- version
- 1
Troubleshooting EFS
Overview
Domain expertise for diagnosing and resolving Amazon EFS issues. Covers mount failures, NFS connectivity, IAM and POSIX permissions, throughput and performance, and encryption problems.
For authoritative guidance, see EFS Troubleshooting.
Common Tasks
0. Verify Dependencies
- You MUST verify
awsCLI is available - You MUST check if
amazon-efs-utilsornfs-utilsis installed on the instance - You MUST ONLY check for tool existence and version — MUST NOT execute destructive or mutating commands during verification
- You MUST inform the user if any required tools are missing
- You MUST respect the user's decision to abort if tools are unavailable
- You SHOULD explain what each step does and why before executing it
- You SHOULD display write commands and wait for user confirmation before executing
1. Classify the Issue
| Symptom | Category |
|---|---|
| "wrong fs type" or mount command fails | A: Missing NFS Client |
| Connection timed out (hangs 2+ min) | B: Network/Security Group |
| "access denied by server" | C: IAM/Permissions |
| Slow throughput or high latency | D: Performance |
| NFS server error on encrypted FS | E: Encryption/KMS |
| DNS name resolution fails | F: VPC DNS |
2. Category A — Missing NFS Client
# Amazon Linux / RHEL / CentOS
sudo yum -y install amazon-efs-utils # preferred (includes mount helper + TLS)
# OR
sudo yum -y install nfs-utils
# Ubuntu / Debian
sudo apt-get install nfs-common3. Category B — Network/Security Group
Connection timeout is the #1 EFS mount failure — almost always security groups.
- Verify mount target exists in the instance's AZ:
aws efs describe-mount-targets --file-system-id fs-ID --region REGIONVerify security groups — check BOTH directions:
- Mount target SG:
aws ec2 describe-security-groups --group-ids sg-MT— MUST have inbound TCP 2049 from compute SG - Compute SG: MUST have outbound TCP 2049 to mount target SG
- Quick fix:
aws ec2 authorize-security-group-ingress --group-id sg-MT --protocol tcp --port 2049 --source-group sg-COMPUTE
- Mount target SG:
Test connectivity:
nc -zv fs-ID.efs.REGION.amazonaws.com 2049Note: These security group troubleshooting steps also apply to S3 Files. The only difference is S3 Files uses
aws s3files list-mount-targetsinstead ofaws efs describe-mount-targets.
4. Category C — IAM/Permissions
"access denied by server" with -o iam:
- Check identity-based IAM policy has
elasticfilesystem:ClientMount - Check file system resource policy:
aws efs describe-file-system-policy --file-system-id fs-ID --region REGIONNote: IAM authorization is only enforced when a file system policy exists that requires it. Without a file system policy, any client in the VPC with port 2049 access can mount — even with -o iam. To enforce IAM, you MUST create a file system policy that denies anonymous access.
POSIX permission denied (not IAM):
- Check file/directory ownership:
ls -la /mnt/efs/ - Use access points to enforce UID/GID for consistent permissions
Show full SKILL.md (243 more words)Show less
5. Category D — Performance
Check throughput mode:
aws efs describe-file-systems --file-system-id fs-ID --region REGION --query 'FileSystems[0].ThroughputMode'Burst credit exhaustion (Bursting mode only):
aws cloudwatch get-metric-statistics --namespace AWS/EFS --metric-name BurstCreditBalance --dimensions Name=FileSystemId,Value=fs-ID --period 3600 --statistics Average --start-time $(date -u -d '24 hours ago' +%Y-%m-%dT%H:%M:%S) --end-time $(date -u +%Y-%m-%dT%H:%M:%S)If credits near zero, switch to Elastic throughput:
aws efs update-file-system --file-system-id fs-ID --throughput-mode elastic --region REGIONGeneral Purpose vs Max I/O:
- Check
PercentIOLimitmetric — if consistently >80%, consider Max I/O - Note: performance mode is IMMUTABLE — must create new FS and migrate
6. Category E — Encryption/KMS
NFS server error on encrypted FS = KMS key issue.
- Verify key is enabled in KMS console
- Verify EFS service-linked role has KMS permissions
- If key deleted: cancel deletion if within grace period
7. Category F — VPC DNS
DNS resolution failure = VPC DNS settings disabled.
aws ec2 describe-vpc-attribute --vpc-id vpc-ID --attribute enableDnsHostnames
aws ec2 describe-vpc-attribute --vpc-id vpc-ID --attribute enableDnsSupportBoth MUST be true. If not:
aws ec2 modify-vpc-attribute --vpc-id vpc-ID --enable-dns-hostnames Value=true
aws ec2 modify-vpc-attribute --vpc-id vpc-ID --enable-dns-support Value=trueTroubleshooting
Mount hangs then times out
Most common cause: security group. Verify TCP 2049 is open between compute and mount target.
Auto-mount fails on reboot
/etc/fstab entry MUST include _netdev option to wait for network before mounting.
"nfs not responding" after reconnect
Old kernel bug with TCP port reuse. Update kernel or add noresvport mount option.
Enable Debug Logs
Set logging_level = DEBUG in /etc/amazon/efs/efs-utils.conf. Logs at /var/log/amazon/efs/mount.log.
Collect Logs for AWS Support
sudo tar -czf /tmp/efs-logs.tar.gz /var/log/amazon/efs/ /etc/amazon/efs/efs-utils.confSecurity Considerations
- IAM authorization is only enforced when a file system policy exists — without one, any VPC client with port 2049 access can mount
- When troubleshooting access denied, verify both identity-based and resource-based policies
- Use
-o tlsfor encryption in transit — unencrypted NFS traffic is visible on the network - Restrict
/var/log/amazon/efs/access — logs may contain file system IDs and mount target IPs
Additional Resources
© aws, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/specialized-skills/storage-skills/troubleshooting-efs of aws/agent-toolkit-for-aws.
Open the folder on GitHubat commit df2ab44
Compare with similar skills
Troubleshooting Efs next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Troubleshooting Efs this skillaws/agent-toolkit-for-aws | 2.8k | — | ~1.6k | Automated safety check: Notes | Apache-2.0 | |
| Cloud Auditbriiirussell/cybersecurity-skills | 413 | — | ~1.3k | Automated safety check: Notes | MIT | |
| Ecs Operation Reviewaws/tools-for-devops-agent | 102 | — | ~4.8k | Automated safety check: Pass | Apache-2.0 | |
| Iamitsmostafa/aws-agent-skills | 1.2k | — | ~1.8k | Automated safety check: Pass | MIT | |
| AWS Security ArchitectureHack23/cia | 239 | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| AWS Iamsickn33/agentic-awesome-skills | 47k | 2 repos | ~3.4k | Automated safety check: Pass | MIT |
Similar skills
- Official
Ecs Operation Review
aws/tools-for-devops-agent
Performs a comprehensive Amazon ECS operations review across the 6 review pillars (Resiliency & HA, Observability, Security, Operations, Performance, Additional Analysis) using read-only AWS APIs…
Iam
itsmostafa/aws-agent-skills
AWS Identity and Access Management for users, roles, policies, and permissions.
AWS Security Architecture
Hack23/cia
AWS security best practices, VPC security, IAM, KMS, CloudTrail, GuardDuty for CIA platform deployment
AWS Iam
sickn33/agentic-awesome-skills
Manage IAM users, roles, and policies. An agent skill from sickn33/agentic-awesome-skills.
Performing AWS Account Enumeration With Scout Suite
mukul975/Anthropic-Cybersecurity-Skills
Run the agentless, open-source ScoutSuite tool (via pip install and the scout CLI) against an AWS account to enumerate resources across services, identify misconfigurations, and generate an…
More from aws/agent-toolkit-for-aws
All 138 skills in this repo- Official
Agent Advisor
aws/agent-toolkit-for-aws
Entry point for AI-agent work on AWS: pick a runtime, plan a migration for existing workloads, and build an executable POC — one phased flow.
- Official
Agents Build
aws/agent-toolkit-for-aws
A skill your agent uses to extend an existing agent project with memory, app integration, VPC, multi-agent, migration, model, browser, code interpreter, payments, or resource removal.
- Official
Launch With AWS
aws/agent-toolkit-for-aws
Migrates vibe-coded web applications to AWS. An agent skill from aws/agent-toolkit-for-aws.
- Official
Processing S3 Uploads With Step Functions
aws/agent-toolkit-for-aws
Deploy an event-driven workflow that routes S3 uploads to either Lambda or Fargate via Step Functions based on file size.
- Official
AWS Marketplace Metering
aws/agent-toolkit-for-aws
Deploys, queries, and debugs AWS Marketplace usage-based (PAYG) metering — the pipeline (ResolveCustomer, BatchMeterUsage, EventBridge via SAM) and querying/debugging metering records, statuses…
- Official
Agents Pay
aws/agent-toolkit-for-aws
A skill your agent uses when THIS agent needs to pay for x402-protected content at runtime: hitting a paywall mid-task, settling it via AgentCore Payments, and applying operator-defined spend limits.
Related
Works with
Categories
Questions about Troubleshooting Efs
What does Troubleshooting Efs do?
Diagnoses and resolves Amazon EFS issues including mount failures, NFS timeouts, permission errors, throughput problems, and burst credit exhaustion. Troubleshooting Efs is an agent skill from aws/agent-toolkit-for-aws, published by the product's own GitHub organization. Diagnoses and resolves Amazon EFS issues including mount failures, NFS timeouts, permission errors, throughput problems, and burst credit exhaustion.
When should I use Troubleshooting Efs?
Troubleshooting Efs fits situations like: the user has an EFS file system that is not mounting; returning errors; performing slowly; showing access denied.
How do I install Troubleshooting Efs in Claude Code?
Run `npx skills add aws/agent-toolkit-for-aws --skill troubleshooting-efs -a claude-code`. Or copy the skill folder (skills/specialized-skills/storage-skills/troubleshooting-efs in aws/agent-toolkit-for-aws) into .claude/skills/troubleshooting-efs in your project. Claude Code loads it when a task matches its description.
How do I install Troubleshooting Efs in Codex?
Run `npx skills add aws/agent-toolkit-for-aws --skill troubleshooting-efs -a codex`. Or copy the skill folder (skills/specialized-skills/storage-skills/troubleshooting-efs in aws/agent-toolkit-for-aws) into .agents/skills/troubleshooting-efs in your project. Codex loads it when a task matches its description.
Can I use Troubleshooting Efs in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aws/agent-toolkit-for-aws --skill troubleshooting-efs -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/troubleshooting-efs, .gemini/skills/troubleshooting-efs, .github/skills/troubleshooting-efs and .opencode/skills/troubleshooting-efs in your project.
What does Troubleshooting Efs need to run?
Going by SKILL.md and its folder, Troubleshooting Efs needs the command-line tools its instructions call (aws, yum and apt-get).
Does Troubleshooting Efs access the network?
SKILL.md names 1 domain. As links in the text: docs.aws.amazon.com. This is read from the text; nothing was executed.
Is Troubleshooting Efs safe to install?
Our automated static check of SKILL.md found notes only (runs commands with sudo), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Troubleshooting Efs use?
Troubleshooting Efs is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Troubleshooting Efs use?
About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Troubleshooting Efs?
Skills that share tags, products or a category with Troubleshooting Efs: Cloud Audit (briiirussell/cybersecurity-skills, 413 stars), Ecs Operation Review (aws/tools-for-devops-agent, 102 stars), Iam (itsmostafa/aws-agent-skills, 1.2k stars) and AWS Security Architecture (Hack23/cia, 239 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Troubleshooting Efs?
aws (a GitHub organization, an official publisher) maintains it in aws/agent-toolkit-for-aws, which has 2,830 GitHub stars. The repository holds 138 skills in this directory. The repository was last updated on October 9, 2026.
Source: aws/agent-toolkit-for-aws on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.