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 agentmods add skills/facebook/agentic-tools/compliance-checknpx skills add facebook/agentic-tools --skill compliance-checkgit clone --depth 1 https://github.com/facebook/agentic-toolsWrote 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/facebook/agentic-tools/compliance-check)<a href="https://agentmods.dev/skills/facebook/agentic-tools/compliance-check"><img src="https://agentmods.dev/badge/skills/facebook/agentic-tools/compliance-check.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 | $0.00036 | $0.00801 |
| Opus 5 | $0.00018 | $0.00400 |
| Sonnet 5 | $0.00007 | $0.00160 |
| Haiku 4.5 | $0.00004 | $0.00080 |
Grade A, and why
compliance-check 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 4d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compliance Check
Audit the compliance posture of a Meta app and provide remediation guidance.
Workflow
-
Start tracking. Before any other work, call
devtools_skill_invocationwith actionstartandskill_namecompliance-check. Passskill_namecompliance-checkon everydevtools_*tool call in the following steps. -
Identify the app. Ask the user for the app name or ID. If they give a name (or aren't sure of the ID), call
devtools_app_list(actionlist) and resolve it to anapp_id— match the name case-insensitively. If several apps match or it's ambiguous, show the candidates (name, ID, viewer role) and ask the user to pick. If they give a numeric ID, use it directly. -
Collect data in parallel:
devtools_compliancewith actionstatus— full compliance statusdevtools_appwith actionbasic_settings— app context (name, category, status)devtools_appwith actiondata_protection_officer— DPO contact info
-
Analyze compliance status. Categorize findings by severity:
Violations (critical — may result in app restrictions or removal)
- What the violation is
- When it was flagged
- What action is required
- Deadline for resolution
Required Actions (high — must be completed by deadline)
- Description of the required action
- Deadline
- Steps to complete
Recommendations (low — suggested improvements)
- What's recommended and why
- How to implement
-
Produce the compliance report:
Report Format
App Overview
- App name, ID, category
Compliance Score
- Overall status: COMPLIANT / ACTION REQUIRED / VIOLATION
- Count of items by severity
Violations (if any)
- Each violation with description, deadline, and remediation steps
Required Actions (if any)
- Each action with description, deadline, and steps to complete
Recommendations (if any)
- Each recommendation with description and implementation guidance
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.
- 4d ago First seen · 80 lines · 36 tokens per session scan A a9b93aa276df
compliance-check is a skill published in the GitHub repository facebook/agentic-tools (6 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 801 once invoked, about $0.0002 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
tooluniverse-drug-research
Comprehensive drug profiling — mechanism, primary/secondary targets, drug interactions, clinical-trial status, adverse events (FAERS), pharmacogenomics, and approval history. Use for full drug investigation reports, 'tell me about drug X' queries, and assembling drug profiles for clinicians, researchers, or regulatory…
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
catalyst-center-readonly
Query Cisco Catalyst Center read-only — device inventory, site hierarchy, wireless, assurance health, compliance, software images, events. All 514 read-only API operations reachable through 8 grouped dispatchers. Use when asked what Catalyst Center manages, where a device sits, what its health or compliance state is…
build-audit-logs
Build or review audit trails in TypeScript/JavaScript apps using evlog (pipelines, typed actions, denials, retention, compliance-style reviews). For application code, not for extending the evlog package.
nda-review
Use when the user uploads or pastes a non-disclosure agreement and asks for review, redline, risk assessment, or a recommendation on whether to sign. Identifies missing standard protections, one-sided or unusual provisions, and operational issues; produces a structured report with severity ratings and citations to…