What is aid-design-cicd?

A skill for designing a CI/CD delivery pipeline. CI/CD means automatically building, checking, and moving software toward release through defined stages and environments.

Use it to outline pipeline stages, triggers, environments, promotion rules, and release flow in a design seed. It does not create the final pipeline or deploy software.

It helps settle how software should be built, checked, promoted, and released before those decisions are recorded in the project. It keeps the design separate from actually creating the pipeline.

aid-design-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-design-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-design-cicd/github.svg)](https://agentmods.dev/skills/andrevianna/aid-methodology/aid-design-cicd)

Your own site

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

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

When invoked 1,189 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.00187	$0.01189
Opus 5.5	$0.00075	$0.00476
Sonnet 5.5	$0.00037	$0.00238
Haiku 4.5	$0.00019	$0.00119

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

Security

Grade A, and why

aid-design-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.

.agents/skills/aid-design-cicd/SKILL.md · 101 lines

How it starts

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

Design CI/CD (develop a design seed, resolve nothing)

Bind VERB=design, ARTIFACT=cicd -- the design 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. The seed it writes is .aid/design/cicd.md; realizing it into the project's C8 document is /aid-create-cicd's job, not this one's.

Boundary vs /aid-create-cicd: that skill realizes the seed into the C8 document; this one only develops the seed. Neither resolves anything on its own.
Boundary vs /aid-design-infra, /aid-design-data-pipeline and /aid-deploy: /aid-design-infra designs a resource the pipeline ships to; /aid-design-data-pipeline designs a data pipeline, not a delivery one; /aid-deploy ships a built artifact.
Not a numbered pipeline phase; does not route to /aid-execute.

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

State: INTAKE

Require a subject. Empty argument -> ask one bootstrapping question ("What delivery pipeline do you want to design -- its stages, triggers, environments, and promotion flow?") 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-design-cicd. phase is not driven.
Acquire .aid/design/ per the contract, then read .aid/design/cicd.md if a prior seed exists -- re-invocation iterates it rather than starting over.
Classify complexity for the aid-architect dispatch (verifier tier >= producer).

Advance: DESIGN.

State: DESIGN

Dispatch aid-architect (clean context, tiered) to write or iterate .aid/design/cicd.md in the seed shape the contract fixes (design-seed.md; feature-002 §4), grounded in .aid/knowledge/ and the project source plus any seed read in INTAKE. What this artifact's seed must settle: the pipeline stages, triggers, environments, and promotion and release flow.

Read the full file on GitHub · 101 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 288211ce455c
2mo ago First seen · 101 lines · 187 tokens per session scan A 20e8eedd4b85

Subscribe to this mod's changes

aid-design-cicd is a skill published in the GitHub repository AndreVianna/aid-methodology (6 stars, last pushed 11d ago), licensed MIT. It adds 187 tokens to every session and 1,189 once invoked, about $0.0007 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-08-31.

CI and CD DevOps and cloud

aid-design-cicd next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
aid-design-cicdAndreVianna/aid-methodology	Skill	6	11d ago	MIT	A	187	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