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 AndreVianna/aid-methodology --skill aid-create-cicdgit clone --depth 1 https://github.com/AndreVianna/aid-methodologyWrote 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/andrevianna/aid-methodology/aid-create-cicd)<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-create-cicd"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-create-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.
<a href="https://agentmods.dev/skills/andrevianna/aid-methodology/aid-create-cicd"><img src="https://agentmods.dev/badge/skills/andrevianna/aid-methodology/aid-create-cicd.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.00205 | $0.02267 |
| Opus 5 | $0.00102 | $0.01133 |
| Sonnet 5 | $0.00041 | $0.00453 |
| Haiku 4.5 | $0.00020 | $0.00227 |
Grade A, and why
aid-create-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 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create CI/CD (realize a seed into the C8 document)
Bind VERB=create, ARTIFACT=cicd -- the create stage in the contract's
vocabulary -- then follow the shared contract at
.claude/aid/templates/design-lifecycle.md. This skill binds that contract and restates
none of its rules. It consumes the seed /aid-design-cicd produces and touches
.aid/design/ for no other purpose.
- Boundary vs
/aid-update-cicd: that skill revises C8 content this lifecycle already committed; this one realizes a seed. - Boundary vs the resource and data-pipeline skills:
/aid-create-infraand/aid-update-infraprovision or change a resource;/aid-create-data-pipelineand/aid-update-data-pipelinebuild a data pipeline;/aid-deployships a built artifact. This one writes the KB's C8 delivery-pipeline record. - Not a numbered pipeline phase; does not route to
/aid-execute.
State machine: INTAKE -> CREATE -> VERIFY -> PRESENT -> DONE, as
design-lifecycle.md § Skill shape defines it. Print the [State: NAME] -- {purpose} entry
line on each state.
State: INTAKE
- Allocate through the Work Initiation Gate exactly as the contract's Allocation rule
requires (
.claude/skills/aid-design/SKILL.mdINTAKE step 4 is the shape), withinitiator: aid-create-cicd.phaseis not driven. - Read the seed at
.aid/design/cicd.md. - Resolve the destination by concern, not filename. This skill binds concern C8
(shipping & operation,
.claude/aid/templates/kb-authoring/concern-model.md). The seed's## Destinationnames the resolved path; where it does not, resolve C8 against.aid/settings.ymlknowledge.doc_set, falling back to the C8 row of.claude/aid/templates/kb-authoring/domain-doc-matrix.md, and confirm with the user. An ambiguous realization is asked, never picked silently. - Read the whole destination if it exists, and note its
source:field. - Ask whether the user also wants production config this run. Emitting a workflow file is opt-in per run and never the default; the KB record is what this skill writes unless the user asks in this run.
- Classify complexity for the
aid-architectdispatch (verifier tier >= producer).
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 · 191 lines · 205 tokens per session scan A 286aade829fd
aid-create-cicd is a skill published in the GitHub repository AndreVianna/aid-methodology (5 stars, last pushed 2d ago), licensed MIT. It adds 205 tokens to every session and 2,267 once invoked, about $0.0010 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
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.