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 lukasrepublic/agentic-foundry --skill cicd-gitops-pipelinegit clone --depth 1 https://github.com/lukasrepublic/agentic-foundryWrote 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/lukasrepublic/agentic-foundry/cicd-gitops-pipeline)<a href="https://agentmods.dev/skills/lukasrepublic/agentic-foundry/cicd-gitops-pipeline"><img src="https://agentmods.dev/badge/skills/lukasrepublic/agentic-foundry/cicd-gitops-pipeline.svg" alt="Measured on agentmods" 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.00000 | $0.01431 |
| Opus 5 | $0.00000 | $0.00715 |
| Sonnet 5 | $0.00000 | $0.00286 |
| Haiku 4.5 | $0.00000 | $0.00143 |
Grade B, and why
cicd-gitops-pipeline scanned grade B with 2 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 7d 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
`wget --post-data` with a printf-built payload — never `apk add curl jq` under a restricted Pod Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`wget --post-data` with a printf-built payload — never `apk add curl jq` under a restricted Pod How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to trigger
- Standing up the delivery pipeline for a service migrating onto the EKS/GitOps target (new CI job, registry repo, gitops values file, or ApplicationSet entry).
- Debugging a registry push 403/400, a service that "deployed but didn't change", or notifications that double-post or go silent.
- Onboarding an externally-hosted (GitHub-origin) repo into the same delivery contract.
The pipeline shape (six parts, one contract)
- Shared CI build template. Every service
include:s ONE shared build template and sets only a few per-app variables (APP_NAME,REGISTRY_REPO,DOCKERFILE,VALUES_FILE,DEPLOY_BRANCH). Build logic lives in exactly one place — a gotcha fixed in the template is fixed for the fleet. - Rootless build → immutable commit-SHA tag. The image is built rootless (BuildKit) and pushed
to an immutable-tag registry where the tag IS the commit SHA (
imageTagMutability: IMMUTABLEis a supply-chain control, never a nuisance to disable). - GitOps write-back. On a successful deploy-branch build, a bot bumps
image.tagin the service's values file in the gitops repo (push or auto-merged MR). The write-back is the ONLY bridge from CI to CD — nokubectl/helmfrom CI. - ApplicationSet over the ONE shared multi-tenant workload chart. Each service is one generator entry rendering the shared chart — never a bespoke Application per service.
- One-line activation, sync-wave ordered. A service goes live by uncommenting exactly one generator/app-of-apps path line and is DARK until then; ordering across services is sync-waves, not merge timing.
- Dual-channel notifications, label-scoped. CI build/deploy lifecycle (started/succeeded/failed) posts to the CI channel FROM the build side; ArgoCD sync/health (sync-running/succeeded/failed/ health-degraded) posts to a SEPARATE gitops channel FROM the CD controller's notification subscriptions. The ApplicationSet stamps a label on each generated Application and the subscriptions match ONLY that label — platform apps carry no label and stay silent; nothing double-posts (each channel has exactly one 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.
- 7d ago First seen · 87 lines · 0 tokens per session scan B 65622531705b
cicd-gitops-pipeline is a skill published in the GitHub repository lukasrepublic/agentic-foundry (1 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,431 tokens. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
yolo-finish
Use when a feature is implemented and verified, to land it. Default path is PR + CI check, with the ship gate confirming before the irreversible merge; fast-local is the escape hatch. Includes the risk classifier whose hard triggers always stop for a human. Triggers on "ship it", "land this", "open a PR", or as the…
turborepo-caching
Configure Turborepo for efficient monorepo builds with local and remote caching. Use when setting up Turborepo, optimizing build pipelines, or implementing distributed caching.
pipeline-digest
Daily release-pipeline digest with a change gate — reports which plugins are pending release, whether main's CI is green, and which branches went stale, and notifies the operator only when that state actually moved since the last run. Use when the operator asks "what moved in the pipeline", "anything to ship"…
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
ci-pipeline
Push current branch and return the pipeline tracking URL (GitLab or GitHub Actions).
ci-status
Show current pipeline status for the active branch (GitLab CI or GitHub Actions).