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 wardawgmalvicious/agent-config --skill fabric-cicdgit clone --depth 1 https://github.com/wardawgmalvicious/agent-configWrote 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/wardawgmalvicious/agent-config/fabric-cicd)<a href="https://agentmods.dev/skills/wardawgmalvicious/agent-config/fabric-cicd"><img src="https://agentmods.dev/badge/skills/wardawgmalvicious/agent-config/fabric-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/wardawgmalvicious/agent-config/fabric-cicd"><img src="https://agentmods.dev/badge/skills/wardawgmalvicious/agent-config/fabric-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.00244 | $0.04608 |
| Opus 5 | $0.00122 | $0.02304 |
| Sonnet 5 | $0.00049 | $0.00922 |
| Haiku 4.5 | $0.00024 | $0.00461 |
Grade A, and why
fabric-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 yesterday.
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 — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fabric-cicd (Python deployment library)
Microsoft's official open-source Python library for code-first CI/CD into Fabric workspaces. It abstracts the Fabric REST item-definition APIs: point it at a Git checkout of a Fabric Git-synced workspace folder and it publishes every in-scope item into the target workspace.
Version / install: current is v1.3.x (August 2026). pip install fabric-cicd (or uv add fabric-cicd). Python 3.9–3.13. Docs: microsoft.github.io/fabric-cicd · repo: github.com/microsoft/fabric-cicd.
v1.0 (April 2026) was a breaking release: token_credential became required — the DefaultAzureCredential fallback and implicit Fabric-notebook auth were removed. Any pre-1.0 sample that omits the credential no longer runs.
Which deployment surface am I on?
| Surface | Source of truth | When |
|---|---|---|
| fabric-cicd (this skill) | Git | Python-scripted deploys in ADO / GitHub Actions / notebooks; finest control (feature flags, orphan cleanup, selective publish) |
fab deploy --config config.yml |
Git | Same engine, CLI wrapper — one-command deploys; see fabric-cli skill |
| Fabric deployment pipelines (service-side) | Workspace | Dev workspace promoted stage-to-stage in the portal / REST; no local code involved |
fab deploy wraps fabric-cicd and consumes the same config.yml / parameter.yml. Don't mix Git-driven deploys and service-side deployment pipelines on the same workspaces. Decision guide: Choose the best Fabric CI/CD workflow.
Deployment pipelines don't rewrite OneLake image URLs. A report whose visuals source images from OneLake carries the workspace GUID inside the URL itself:
https://onelake.dfs.fabric.microsoft.com/<workspace-guid>/<item-guid>/Files/<path>/<file-name>
Promote that report dev → test → prod through a service-side deployment pipeline and it keeps loading its images from the original workspace. Nothing fails and nothing warns — the report renders, the images appear — until access to the source workspace is revoked or it is deleted, long after the promotion. Upstream's remedies are to parameterize the URLs or rewrite them after deployment.
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.
- yesterday Changed e7e8fe86c9aa
- 2d ago Changed · +27 lines cf539043629e
- 6d ago Changed · +3 lines dc6d6fd05482
- 10d ago First seen · 289 lines · 244 tokens per session scan A 1201bb0bcc79
fabric-cicd is a skill published in the GitHub repository wardawgmalvicious/agent-config (0 stars, last pushed today), licensed MIT. It adds 244 tokens to every session and 4,608 once invoked, about $0.0012 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
azure-validate
WORKFLOW SKILL — Pre-deployment validation for Azure: config, infrastructure (Bicep/Terraform), permissions, prerequisites. WHEN: 'validate my app', 'check deployment readiness', 'run preflight checks', 'validate azure.yaml', 'validate Bicep', 'test before deploying', 'validate Azure Functions'. DO NOT USE FOR…
iac-common
UTILITY SKILL — Shared IaC deploy patterns for Bicep + Terraform agents: deployment strategies, circuit breaker, known deploy issues. WHEN: "phased deployment", "circuit breaker", "deploy strategy", "deploy issue", "shared IaC pattern". DO NOT USE FOR: preflight (azure-validate), code generation (azure-bicep-patterns…
azure-deploy
WORKFLOW SKILL — Execute Azure deployments (azd up, azd deploy, terraform apply) for already-prepared apps with built-in error recovery. WHEN: 'run azd up', 'run azd deploy', 'push to production', 'go live', 'bicep deploy', 'terraform apply', 'publish to Azure'. DO NOT USE FOR: creating new apps (azure-prepare)…
azure-microsoft-playwright-testing-ts
Run Playwright tests at scale using Azure Playwright Workspaces (formerly Microsoft Playwright Testing). Use when scaling browser tests across cloud-hosted browsers, integrating with CI/CD pipelines, or publishing test results to the Azure portal.
azure-kubernetes-app-deploy
Use when deploying an existing web application or API to an already-running Azure Kubernetes Service cluster. Detects the framework, generates a Dockerfile and Kubernetes manifests, validates against AKS Deployment Safeguards, and deploys with verification. WHEN: deploy app to AKS, deploy to existing AKS cluster…
bitbucket
Bitbucket code repository integration for managing repos, branches, PRs, issues, and CI/CD pipelines.