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 atezer/FMCP --skill fmcp-ds-audit-orchestratorgit clone --depth 1 https://github.com/atezer/FMCPWrote 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/atezer/fmcp/fmcp-ds-audit-orchestrator)<a href="https://agentmods.dev/skills/atezer/fmcp/fmcp-ds-audit-orchestrator"><img src="https://agentmods.dev/badge/skills/atezer/fmcp/fmcp-ds-audit-orchestrator/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/atezer/fmcp/fmcp-ds-audit-orchestrator"><img src="https://agentmods.dev/badge/skills/atezer/fmcp/fmcp-ds-audit-orchestrator.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.00000 | $0.02753 |
| Opus 5.5 | $0.00000 | $0.01101 |
| Sonnet 5.5 | $0.00000 | $0.00551 |
| Haiku 4.5 | $0.00000 | $0.00275 |
Grade A, and why
fmcp-ds-audit-orchestrator 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FMCP DS Audit Orchestrator
Essentials (Üst Bölüm — %80 Case İçin Yeterli)
Ortak Protokol (Condensed — full: agents/_orchestrator-protocol.md)
- Skill Registry açık — tahmin yasak
- Intent Routing — belirsizse Read fmcp-intent-router
- Cheap-First —
depth=1,verbosity="summary"; SEVERE bulgu varsa ilgili alt ağaca drill-down - Cache-First —
.claude/audits/<YYYY-MM-DD>-<nodeId>.md24h freshness; 30 günden eski dosyaları temizle - User Onay — hiçbir fix uygulanmaz, sadece önerilir (read-only discipline)
- Self-Audit — her SEVERE kategori için ≥1 somut nodeId raporda olmalı
- Skill Evolution — iki aşamalı onay, DRAFT banner
- Türkçe raporlama — metrik bloğu sonunda; CI için JSON mode destekli
Skill Registry (Ref Only — Read() sadece karar anında)
| Skill | Dosya yolu | Trigger | Common case lazım mı? |
|---|---|---|---|
audit-figma-design-system |
skills/audit-figma-design-system/SKILL.md |
Genel DS compliance | Compliance modunda |
figma-a11y-audit |
skills/figma-a11y-audit/SKILL.md |
A11y / erişilebilirlik | A11y modunda |
design-drift-detector |
skills/design-drift-detector/SKILL.md |
Code↔Figma drift | Drift modunda |
visual-qa-compare |
skills/visual-qa-compare/SKILL.md |
Figma vs code görsel fark | Visual QA modunda |
ds-impact-analysis |
skills/ds-impact-analysis/SKILL.md |
Değişiklik risk skoru | Impact modunda |
fix-figma-design-system-finding |
skills/fix-figma-design-system-finding/SKILL.md |
Tek bulgu fix ÖNERİSİ | Sadece fix önerme aşamasında |
apply-figma-design-system |
skills/apply-figma-design-system/SKILL.md |
Tüm ekran hizalama ÖNERİSİ | Sadece toplu fix önerme |
Audit Type Routing
| Kullanıcı ifadesi | Mod | Read skill |
|---|---|---|
| "DS uyumu", "compliance", "denetle", "token bağlı mı" | compliance |
audit-figma-design-system |
| "erişilebilirlik", "a11y", "kontrast", "WCAG", "screen reader" | a11y |
figma-a11y-audit |
| "kod ile tutarsızlık", "drift", "değer kaymış" | drift |
design-drift-detector |
| "code vs figma", "görsel fark", "pixel diff" | visual_qa |
visual-qa-compare |
| "bu değişiklik neyi etkiler", "riskli mi", "impact" | impact |
ds-impact-analysis |
| Net değil / çoklu istek | auto |
AskUserQuestion ile sor (veya düz metin soru) |
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 · 206 lines · 0 tokens per session scan A d9d47f214f3d
fmcp-ds-audit-orchestrator is a skill published in the GitHub repository atezer/FMCP (10 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,753 tokens. 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
accessibility-per-component
Audit one design system component's accessibility against WCAG 2.2 AA: keyboard, screen reader, contrast, focus, ARIA, target size. Trigger: a11y audit, is this accessible, WCAG check, screen reader support, keyboard navigation check. Not for page- or product-wide audits.
schema-validator
Validate token files structurally against DTCG 2025.10 (including resolvers), Style Dictionary 3 to 5 or Tokens Studio: parse errors, $type/$value, name rules, broken or circular aliases. Trigger: validate token JSON, DTCG compliance, are my token files valid. Naming or architecture: token-audit.
design-fidelity-verify
Prove a running app matches its design spec by measuring rendered values, not eyeballing a screenshot. Use when the user says "verify the design", "is this pixel-perfect", "check against Figma", "does the app match the design", or "design QA this screen". Runs a bounded vision+numeric loop over web or mobile…
figma-variable-audit
Audit Figma variable collections: tier mapping, naming, alias chains, modes, orphans; can fix in place with Figma Console MCP. Triggers: audit my Figma variables, review variable collections, Figma variable health. For token files in code use token-audit.
theme-audit
Audit theme parity: tokens missing or unchanged per theme, component tokens bypassing semantics, contrast within each theme, resolver contexts, theme-switch regressions. Triggers: dark mode audit, theme coverage, brand variant parity. For general token structure use token-audit.
token-audit
Audit how design tokens are defined: tiers, naming, alias chains, raw values, orphans, DTCG readiness. Triggers: audit my tokens, token architecture review, token health check. Not for code consuming tokens (token-compliance), theme parity (theme-audit) or Figma variables (figma-variable-audit).