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-deploygit 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-deploy)<a href="https://agentmods.dev/skills/wardawgmalvicious/agent-config/fabric-deploy"><img src="https://agentmods.dev/badge/skills/wardawgmalvicious/agent-config/fabric-deploy/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-deploy"><img src="https://agentmods.dev/badge/skills/wardawgmalvicious/agent-config/fabric-deploy.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.00112 | $0.02765 |
| Opus 5.5 | $0.00045 | $0.01106 |
| Sonnet 5.5 | $0.00022 | $0.00553 |
| Haiku 4.5 | $0.00011 | $0.00277 |
Grade A, and why
fabric-deploy 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 14d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploying Fabric content
A deploy moves item definitions from a source, a Git branch or a workspace, into a target workspace. Four routes do it, each with its own reference; this file picks one and wraps it in the steps every route shares. Take them in order: a wrong route invalidates every step after it.
1. Pick the route
| Source of truth | Route | Learn's option | Read |
|---|---|---|---|
| Git, one branch pushed to each stage by a script or CI | the fabric-cicd Python library | 2 | fabric-cicd.md |
| Git, the same in one command | fab deploy --config, which wraps the library and reads its config.yml and parameter.yml |
2 | fab-deploy.md, then fabric-cicd.md |
| Git, a branch per stage, each stage's workspace connected | Git integration's Update From Git | 1 | fabric-rest-api § Git Integration APIs |
| The workspace: dev promoted to test and prod in the service | deployment pipelines | 3 | deployment-pipelines.md |
Learn's option 2 also names the Bulk Import Item Definitions API, which
the library calls under enable_bulk_publish; Learn's
tutorial
calls it directly.
Never deploy into one workspace by both routes. The library makes its target match the repository, overwriting whatever a pipeline promoted, and an item a Git route adds to a pipeline stage is not paired with its source (deployment-pipelines.md § Item pairing and autobinding). Git on the first stage with pipelines onward is not a mix: it is option 3, whose source of truth Learn gives as "Fabric workspace (Git only through dev)" (read 2026-10-09). Decision guide: Choose the best Fabric CI/CD workflow.
2. Preflight, every route
Identity. Name the identity the deploy will run as, and check:
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 14d ago Changed · +10 lines 1f1c746c5382
- 16d ago First seen · 185 lines · 112 tokens per session scan A 12f83a4f0ffc
fabric-deploy is a skill published in the GitHub repository wardawgmalvicious/agent-config (1 stars, last pushed 11d ago), licensed MIT. It adds 112 tokens to every session and 2,765 once invoked, about $0.0004 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-10-13.
Other skills, from other repositories
aws-ci-cd-release-engineer
Review AWS CI/CD and release safety across CodePipeline, CodeBuild, CodeDeploy, GitHub Actions, GitLab, artifact provenance, deployment gates, approvals, tests, progressive delivery, rollback, change correlation, and incident-prevention recommendations. Use when AWS releases or pipelines can affect production…
xberg-release
Xberg release on top of the shared release-workflow: task version:sync to bindings and chart, CI/Publish/Benchmarks readiness. Use before a release.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
seed-snapshot-release
An automated workflow for creating and tracking a snapshot release of the pull request on the current branch. A snapshot release is a temporary package build used for testing a branch before a normal release.
multi-repo-release
Prepares and validates GPT-RAG umbrella and multi-repository releases. Use whenever work involves release preparation, semantic versions, release branches, manifest or component pins, changelog release entries, tags, GitHub Release notes, or AI Landing Zone release alignment.
cmux-release
Prefer the /release command. It determines the new version (minor by default), gathers the Changelog line from each PR merged since the last stable tag, updates CHANGELOG.md, runs ./scripts/bump-version.sh, commits, runs ./scripts/release-pretag-guard.sh, then tags and pushes.