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 selvarajmurugesan90/ops-engineering-skills --skill aws-codepipeline-and-codedeploygit clone --depth 1 https://github.com/selvarajmurugesan90/ops-engineering-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/selvarajmurugesan90/ops-engineering-skills/aws-codepipeline-and-codedeploy)<a href="https://agentmods.dev/skills/selvarajmurugesan90/ops-engineering-skills/aws-codepipeline-and-codedeploy"><img src="https://agentmods.dev/badge/skills/selvarajmurugesan90/ops-engineering-skills/aws-codepipeline-and-codedeploy/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/selvarajmurugesan90/ops-engineering-skills/aws-codepipeline-and-codedeploy"><img src="https://agentmods.dev/badge/skills/selvarajmurugesan90/ops-engineering-skills/aws-codepipeline-and-codedeploy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 30 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 251 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 373 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 375 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00101 | $0.03912 |
| Opus 5 | $0.00051 | $0.01956 |
| Sonnet 5 | $0.00020 | $0.00782 |
| Haiku 4.5 | $0.00010 | $0.00391 |
Grade A, and why
aws-codepipeline-and-codedeploy 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 9d 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 — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS CodePipeline and CodeDeploy
Purpose
AWS CodePipeline orchestrates a release as a sequence of stages, each
containing one or more actions (source, build, test, approval, deploy)
that can run in parallel within a stage, while CodeDeploy handles the
actual deployment mechanics — rolling out a new revision to EC2/on-prem
instances, an ECS service, or a Lambda function according to a
deployment group's configuration and an appspec.yml's lifecycle
hooks. This skill covers the CodePipeline stage/action JSON/YAML structure
and how it integrates with CodeDeploy specifically — not the generic
pipeline-design concepts covered in
ci-cd-pipeline-design,
which apply here too but aren't repeated.
When to use
- Standing up a new CodePipeline for an application already built elsewhere (or with a CodeBuild stage) that needs to deploy via CodeDeploy.
- Writing or debugging an
appspec.ymlwhose lifecycle hooks (BeforeInstall,AfterInstall,ApplicationStart,ValidateService) aren't firing in the expected order, or a hook script exits non-zero. - Configuring a CodeDeploy deployment group's deployment configuration
(in-place vs. blue/green,
CodeDeployDefault.OneAtATimevs. percentage- based) for EC2/on-prem, or the equivalent ECS/Lambda traffic-shifting options. - Adding a manual approval action to a CodePipeline before a production deploy stage.
- Diagnosing a CodePipeline execution stuck or failed at a specific stage/ action, or a CodeDeploy deployment that failed a lifecycle hook or health check.
Prerequisites & environment
- An AWS account with IAM permissions to create/manage CodePipeline pipelines, CodeDeploy applications/deployment groups, and (for EC2/on- prem deploys) an IAM instance profile on target instances allowing the CodeDeploy agent to pull deployment bundles from S3.
- The CodeDeploy agent installed and running on target EC2/on-prem instances (not needed for ECS or Lambda deployment types, which use CodeDeploy's native integration instead).
- A CodePipeline service role with permission to invoke each stage's action provider (CodeCommit/GitHub/S3 for source, CodeBuild for build, CodeDeploy for deploy) — least-privilege scoped per action, not a single account-wide admin role.
- An S3 artifact bucket (CodePipeline's default artifact store, or a specified one) that all pipeline stages can read/write to pass build output between stages.
- For blue/green EC2 deployments: an Elastic Load Balancer (ALB/CLB) already provisioned and referenced in the deployment group config.
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.
- 9d ago First seen · 376 lines · 101 tokens per session scan A 41298002d099
aws-codepipeline-and-codedeploy is a skill published in the GitHub repository selvarajmurugesan90/ops-engineering-skills (38 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 101 tokens to every session and 3,912 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-30.
Other skills, from other repositories
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.
atmos-sbom
Atmos SBOM provenance: CycloneDX and SPDX generation from vendor and Terraform evidence, coverage diagnostics, NTIA validation, and native CI workflow-artifact publication.
atmos-version
Atmos Version Tracker: version tracks, lock files, managed external dependency versions, atmos version track commands, !version, file managers, update policy, pinning, and CI verification.
atmos-cache
Atmos caching: CI cache configuration and commands, GitHub Actions cache integration, Terraform registry cache mirror/list/prune/stats/trust, and cache modernization guidance.