Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Sefyu24/master-iam-skills --skill plan-iam-careergit clone --depth 1 https://github.com/Sefyu24/master-iam-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/sefyu24/master-iam-skills/plan-iam-career)<a href="https://agentmods.dev/skills/sefyu24/master-iam-skills/plan-iam-career"><img src="https://agentmods.dev/badge/skills/sefyu24/master-iam-skills/plan-iam-career/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sefyu24/master-iam-skills/plan-iam-career"><img src="https://agentmods.dev/badge/skills/sefyu24/master-iam-skills/plan-iam-career.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00107 | $0.01697 |
| Opus 5 | $0.00053 | $0.00848 |
| Sonnet 5 | $0.00021 | $0.00339 |
| Haiku 4.5 | $0.00011 | $0.00170 |
Grade A, and why
plan-iam-career scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan an IAM Career
Create a practical IAM career plan. Keep the interview short and the recommendations specific.
Conduct the interview
Ask one question at a time. Use no more than six main questions. Ask a follow-up only when an answer is unclear or missing important evidence. Stop when enough information is available.
Ask about:
- The IAM role or type of work the user wants. If the user is unsure, ask which work they enjoy.
- The country or city where the user lives, where they can legally work, and whether they accept remote work or relocation.
- Up to three target companies or current job postings. Ask for links when available.
- The current role, total relevant work experience, completed education, degree field, and existing certifications.
- Hands-on IAM, security, cloud, networking, and coding experience. Ask for languages, scripts, integrations, labs, or projects. Ask whether the user wants a programming-heavy role.
- The study time available each week and the target date for applying to jobs.
Do not ask for an exact home address, immigration documents, age, gender, or unrelated personal data.
Ask for examples of completed work. Do not depend only on self-ratings.
If the user asks a question during the interview, answer it briefly. Then continue with the next useful question.
Format each interview turn
Make each turn easy to scan on a phone. Use no more than 80 words unless the user asks for an explanation.
Use this format:
**Current signal:** One careful sentence about what the answer suggests.
**Question 2 of 6 — Location**
Where do you live, and where can you work?
Reply with:
- City and country
- Remote: yes or no
- Relocation: yes or no
- Omit Current signal when the answer does not support a useful conclusion.
- Label an extra question as Follow-up. Do not increase the main-question count.
- Give no more than three short reply prompts.
- Do not list several possible roles after each answer.
- Do not repeat the user's answer.
- Treat an early observation as a signal, not a final recommendation.
- Save detailed explanations and role comparisons for the final plan.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 182 lines · 107 tokens per session scan A dec7b270f97c
plan-iam-career is a skill published in the GitHub repository Sefyu24/master-iam-skills (7 stars, last pushed 24d ago), licensed MIT. It adds 107 tokens to every session and 1,697 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
auditing-gcp-iam-permissions
Auditing Google Cloud Platform IAM permissions to identify overly permissive bindings, primitive role usage, service account key proliferation, and cross-project access risks using gcloud CLI, Policy Analyzer, and IAM Recommender.
performing-aws-privilege-escalation-assessment
Performing authorized privilege escalation assessments in AWS environments to identify IAM misconfigurations that allow users or roles to elevate their permissions using Pacu, CloudFox, Principal Mapper, and manual IAM policy analysis techniques.
securing-aws-lambda-execution-roles
Securing AWS Lambda execution roles by implementing least-privilege IAM policies, applying permission boundaries, restricting resource-based policies, using IAM Access Analyzer to validate permissions, and enforcing role scoping through SCPs.
implementing-rbac-hardening-for-kubernetes
Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.
performing-cloud-native-threat-hunting-with-aws-detective
Hunt for threats in AWS environments using Detective behavior graphs, entity investigation timelines, GuardDuty finding correlation, and automated entity profiling across IAM users, EC2 instances, and IP addresses.
detecting-aws-iam-privilege-escalation
Detect AWS IAM privilege escalation paths using boto3 and Cloudsplaining policy analysis to identify overly permissive policies, dangerous permission combinations, and least-privilege violations.