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 PatrickGallucci/fabric-skills --skill fabric-rest-api-remediategit clone --depth 1 https://github.com/PatrickGallucci/fabric-skillsWrote 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/patrickgallucci/fabric-skills/fabric-rest-api-remediate)<a href="https://agentmods.dev/skills/patrickgallucci/fabric-skills/fabric-rest-api-remediate"><img src="https://agentmods.dev/badge/skills/patrickgallucci/fabric-skills/fabric-rest-api-remediate/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/patrickgallucci/fabric-skills/fabric-rest-api-remediate"><img src="https://agentmods.dev/badge/skills/patrickgallucci/fabric-skills/fabric-rest-api-remediate.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.00104 | $0.03120 |
| Opus 5.5 | $0.00042 | $0.01248 |
| Sonnet 5.5 | $0.00021 | $0.00624 |
| Haiku 4.5 | $0.00010 | $0.00312 |
Grade A, and why
fabric-rest-api-remediate 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 1mo 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 — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Microsoft Fabric REST API remediate
Structured diagnostic workflows for identifying and resolving errors when calling Microsoft Fabric REST APIs (https://api.fabric.microsoft.com/v1/).
When to Use This Skill
- Fabric REST API returns an HTTP error (401, 403, 404, 429, 5xx)
- Authentication or token acquisition fails with MSAL
- Service principal or managed identity calls are rejected
- API calls are being throttled (HTTP 429)
- Long running operations (LRO) fail or time out during polling
- Pagination with
continuationTokenstops working or returns incomplete results - Capacity API operations fail (create, update, resume, suspend)
- Need to implement retry logic with exponential backoff for Fabric APIs
- Debugging
errorCodevalues in Fabric API error responses
Prerequisites
- Microsoft Entra ID app registration with appropriate Fabric API permissions
- PowerShell 7+ with
Az.Accountsmodule or MSAL.PS for token acquisition - Access to a Microsoft Fabric workspace (Contributor or higher)
- Tenant setting Service principals can use Fabric APIs enabled (if using service principals)
Quick Diagnostic: Identify Your Error
Start here. Match your HTTP status code to the appropriate workflow.
| HTTP Status | Error Category | Jump To |
|---|---|---|
| 401 | Authentication / Token | Authentication Failures |
| 403 | Permissions / Authorization | Permission Denied |
| 404 | Resource Not Found | Resource Not Found |
| 429 | Throttling / Rate Limit | Throttling |
| 430 | Spark Compute Limit | Capacity Limits |
| 500/502/503 | Server Error | Server Errors |
| 202 then failure | LRO Polling Issue | LRO remediate |
Understanding Fabric Error Responses
Every Fabric API error returns an ErrorResponse object. Always capture the requestId for support escalation.
What ships with it
7 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.
- LICENSE.txt 11 KB
- references/authentication-guide.md 7.5 KB
- references/error-codes-reference.md 7.4 KB
- references/long-running-operations.md 9.5 KB
- scripts/Invoke-FabricApiWithRetry.ps1 6.0 KB runs code
- scripts/Test-FabricApiConnection.ps1 9.8 KB runs code
- templates/Fabric-Api-ErrorHandler.template.ps1 8.9 KB runs code
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.
- 1mo ago First seen · 337 lines · 104 tokens per session scan A e348408c7406
fabric-rest-api-remediate is a skill published in the GitHub repository PatrickGallucci/fabric-skills (17 stars, last pushed 4mo ago), licensed MIT. It adds 104 tokens to every session and 3,120 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-08-30.
Other skills, from other repositories
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
perf
Use when anything in a Phoenix app is slow, times out, or uses too much memory, even if the cause looks obvious. Load it before analyzing or fixing: it runs measured Ecto, LiveView and OTP checks and ranks fixes.
schema-validation
JSON/data schema validation for construction data exchange: API payloads, file imports, BIM exports. Ensure data structure compliance before processing.
interoperability-analyzer
Analyze data interoperability issues in construction projects. Identify format incompatibilities and data loss points.
routeros-mac-telnet
MAC-Telnet protocol (MikroTik Layer-2 terminal/exec over UDP 20561) wire format, session handshake, and MD5 + MTWEI (EC-SRP) authentication. Use when: implementing or debugging a MAC-Telnet client/server, reaching a RouterOS device by MAC address without IP, parsing MAC-Telnet packets, understanding the WinBox-style…
routeros-syntax-inspection
Inspecting and validating RouterOS command/script syntax against a live device via /console/inspect (highlight, completion, syntax, child) and :parse IL. Use when: validating RouterOS commands before execution, explaining or linting RouterOS scripts, building syntax-aware tooling (LSP servers, validators, agent…