What is aid-update-cicd?

A project-maintenance workflow for updating a written record of the continuous integration and delivery pipeline. CI/CD describes how code is checked, built, promoted between environments, and released.

Use it to revise the project's CI/CD knowledge-base document and named related outputs.

It keeps the pipeline documentation accurate when stages, triggers, environments, or promotion rules change.

aid-update-cicd — Skill for Claude Code by AndreVianna/aid-methodology

Install

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.

Any agent

npx skills add AndreVianna/aid-methodology --skill aid-update-cicd

Clone the repo

git clone --depth 1 https://github.com/AndreVianna/aid-methodology

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-update-cicd/github.svg)](https://agentmods.dev/skills/andrevianna/aid-methodology/aid-update-cicd)

Your own site

<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-update-cicd"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-update-cicd/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-update-cicd"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-update-cicd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 210 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,787 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00210	$0.01787
Opus 5.5	$0.00084	$0.00715
Sonnet 5.5	$0.00042	$0.00357
Haiku 4.5	$0.00021	$0.00179

Measured 26d ago against content hash 2132dbd868da, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

aid-update-cicd 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 26d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

aid-update-stack — 91% identical, 101 lines differ

.agents/skills/aid-update-cicd/SKILL.md · 153 lines

How it starts

The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Update CI/CD (revise the C8 document)

Bind VERB=update, ARTIFACT=cicd -- the update stage in the contract's vocabulary -- then follow the shared contract at .aid/runtime/templates/design-lifecycle.md. This skill binds that contract and restates none of its rules.

Boundary vs /aid-create-cicd: that skill realizes a seed and owns the creation path; this one is the maintenance verb. Where the destination is absent this skill routes there rather than standing one up itself.
Boundary vs the resource and data-pipeline skills: /aid-create-infra and /aid-update-infra provision or change a resource; /aid-create-data-pipeline and /aid-update-data-pipeline act on a data pipeline; /aid-deploy ships a built artifact. This one revises the KB's C8 delivery-pipeline record.
Not a numbered pipeline phase; does not route to /aid-execute.

State machine: INTAKE -> UPDATE -> VERIFY -> PRESENT -> DONE, as design-lifecycle.md § Skill shape defines it. Print the [State: NAME] -- {purpose} entry line on each state.

State: INTAKE

Require a stated change. Empty argument -> ask one bootstrapping question ("What should change in the delivery-pipeline record?") and wait.
Allocate through the Work Initiation Gate exactly as the contract's Allocation rule requires (.agents/skills/aid-design/SKILL.md INTAKE step 4 is the shape), with initiator: aid-update-cicd. phase is not driven.
No seed is required. The change stated in this run is a sufficient input, and this skill completes without a seed. Read and consume one when present at .aid/design/cicd.md, carrying its ## Current direction into the destination and deleting it once realized.
Resolve the destination by concern. This skill binds concern C8 (shipping & operation). Where a seed supplied a ## Destination, use it; otherwise apply the concern rule here -- resolve C8 against .aid/settings.yml knowledge.doc_set, falling back to the C8 row of .aid/runtime/templates/kb-authoring/domain-doc-matrix.md -- and confirm the resolution with the user before writing. Never resolve silently.
Read the whole destination, and note its source: field. Absent destination -> route to /aid-create-cicd and write nothing.
Ask whether the user also wants production config this run. Touching a workflow file is opt-in per run and never the default; the KB record is what this skill revises unless the user asks in this run.
Classify complexity for the aid-architect dispatch (verifier tier >= producer).

Read the full file on GitHub · 153 lines

Changes

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.

26d ago Changed 2132dbd868da
2mo ago First seen · 153 lines · 210 tokens per session scan A bd5254191d1e

Subscribe to this mod's changes

aid-update-cicd is a skill published in the GitHub repository AndreVianna/aid-methodology (6 stars, last pushed 11d ago), licensed MIT. It adds 210 tokens to every session and 1,787 once invoked, about $0.0008 per session on Opus 5.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-09-03.

CI and CD DevOps and cloud

aid-update-cicd next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
aid-update-cicdAndreVianna/aid-methodology	Skill	6	11d ago	MIT	A	210	Claude Code
chinese-git-workflowjnMetaCode/superpowers-zh	Skill	8.5k	12d ago	MIT	A	69	Claude Code
atmos-profilescloudposse/atmos	Skill	1.4k	today	Apache-2.0	A	35	Claude Code
webhook-managementhoangsonww/Claude-Code-Agent-Monitor	Skill	1.2k	yesterday	MIT	A	56	Claude Code, Codex
monorepo-managementwshobson/agents	Skill	42k	2d ago	MIT	C	54	Claude Code
managing-github-actions-secretsPostHog/posthog-foss	Skill	728	today	MIT	A	67	Claude Code, Codex
postman-newman-automationLambdaTest/agent-skills	Skill	391	2d ago	MIT	A	156	Claude Code, Codex