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 palisadeemail/palisade-mcp --skill palisadegit clone --depth 1 https://github.com/palisadeemail/palisade-mcpWrote 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/palisadeemail/palisade-mcp/palisade)<a href="https://agentmods.dev/skills/palisadeemail/palisade-mcp/palisade"><img src="https://agentmods.dev/badge/skills/palisadeemail/palisade-mcp/palisade/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/palisadeemail/palisade-mcp/palisade"><img src="https://agentmods.dev/badge/skills/palisadeemail/palisade-mcp/palisade.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.00096 | $0.01190 |
| Opus 5 | $0.00048 | $0.00595 |
| Sonnet 5 | $0.00019 | $0.00238 |
| Haiku 4.5 | $0.00010 | $0.00119 |
Grade A, and why
palisade 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Palisade - email authentication for AI agents
Palisade is an agentic DMARC platform for IT teams and MSPs. It finds every service sending as a domain, drafts the SPF and DKIM fixes each one needs, reads DMARC aggregate reports, and moves the domain to p=reject with a person approving each step.
The canonical copy of this skill is served by the product at https://www.palisade.email/.well-known/agent-skills/palisade/SKILL.md and is generated from the same facts the product site publishes. This file mirrors it for skills.sh and for the plugin in this repository.
When to use
Use this skill when the user or task involves any of the following:
- A domain's mail is failing or being spoofed - "Why is our mail going to spam?", "Someone is sending as our domain"
- Setting up or tightening DMARC - "Write a DMARC record", "Move us to p=reject", "Do we pass Google and Microsoft's sender requirements?"
- Diagnosing SPF or DKIM - "Our SPF has too many lookups", "Which DKIM selector does our CRM use?"
- Reading DMARC reports - "Who sent mail as us last week?", "Which sources fail alignment?"
- Monitoring many domains - an IT team or MSP that wants every client domain watched and remediated
Do NOT use this skill to send or receive email, to look up a mailbox, or for the unrelated Palisade Identity wallet product.
Surfaces
- MCP server at
https://api.palisade.email/mcp(Streamable HTTP). OAuth through Palisade's public connector client (ryKtuiPypMeYMoL1Cmhxtz6BYrEYQbLV, PKCE, no secret). Sign in and pick an organization. API keys and self-registered OAuth clients are not accepted on MCP. - Public MCP endpoint at
https://api.palisade.email/mcp/public:audit_domainandvalidate_spf_includefor any domain, no account or credential. - Discovery:
https://api.palisade.email/.well-known/mcp(endpoint, transport, auth and every tool with its input schema) and the server card athttps://api.palisade.email/.well-known/mcp/server-card.json. - Stdio bridge for clients that cannot speak Streamable HTTP:
npx -y @palisadeemail/mcp. - REST API at
https://api.palisade.email: OpenAPI athttps://api.palisade.email/swagger.json, guide at https://developer.palisade.email/docs/guide. API keys go in HTTP Basic (key as username, empty password) with aPalisade-Versionheader on every request. Credentials walkthrough: https://www.palisade.email/auth.md. - No-auth DNS JSON at
https://www.palisade.email/api/dns?domain=example.com&type=dmarc: dmarc | spf | dkim | mx | bimi | ns | a | all.
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 First seen · 56 lines · 96 tokens per session scan A a5859c4a792f
palisade is a skill published in the GitHub repository palisadeemail/palisade-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 96 tokens to every session and 1,190 once invoked, about $0.0005 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-09-12.
Other skills, from other repositories
email-deliverability
Use when mail already sent lands in spam, is rejected, or fails the Gmail/Yahoo bulk-sender checks and the fix is authentication and reputation, not the sending code: SPF/DKIM/DMARC alignment, domain warmup, spam-complaint rate, one-click unsubscribe, BIMI. NOT putting mail on the wire through a provider API (that is…
dns-doctor
Use for any question about a domain's DNS or email deliverability. Triggers include looking up a record (A, AAAA, CNAME, MX, TXT, SPF, DMARC) or a DKIM selector, checking whether a DNS change has propagated worldwide, the reverse DNS of a mail-server IP, a domain or certificate about to expire, hardening a parked…
analyzing-email-headers-for-phishing-investigation
Parse and analyze email headers (Received chain, Return-Path, Message-ID) to trace the true origin of a phishing email and validate SPF, DKIM, and DMARC results to confirm or rule out sender spoofing. Use when triaging a suspicious or reported email, investigating a phishing incident, or verifying whether a message's…
analyzing-malicious-url-with-urlscan
URLScan.io is a free service for scanning and analyzing suspicious URLs. It captures screenshots, DOM content, HTTP transactions, JavaScript behavior, and network connections of web pages in an isolat.
analyzing-email-headers-for-phishing-investigation
Parse and analyze email headers to trace the origin of phishing emails, verify sender authenticity, and identify spoofing through SPF, DKIM, and DMARC validation.
email-security
DMARC/SPF/DKIM check, email spoofing, SMTP test, and security header analysis.