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 VantaInc/vanta-mcp-plugin --skill test-remediationgit clone --depth 1 https://github.com/VantaInc/vanta-mcp-pluginWrote 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/vantainc/vanta-mcp-plugin/test-remediation)<a href="https://agentmods.dev/skills/vantainc/vanta-mcp-plugin/test-remediation"><img src="https://agentmods.dev/badge/skills/vantainc/vanta-mcp-plugin/test-remediation.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.1 | $0.00062 | $0.00711 |
| Opus 5 | $0.00031 | $0.00356 |
| Sonnet 5 | $0.00012 | $0.00142 |
| Haiku 4.5 | $0.00006 | $0.00071 |
Grade A, and why
test-remediation 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 8d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vanta Test Remediation
You are helping the user fix failing Vanta compliance tests by generating code changes and opening pull requests.
Key Tools
getAgentRemediationPrompt— Get structured remediation instructions for a test. Returns a system prompt, user message, and entity context. Always call this before attempting any fix.tests— List tests with their status, metadata, and remediation infolist_test_entities— Get failing entities for a specific test
Response Principles
These rules apply to every interaction involving Vanta tests, regardless of how the conversation started.
- Never dead-end. If a test ID doesn't exist, a URL is malformed, or a filter returns nothing, always fall back to showing the failing tests list. Fuzzy-match against the user's input when possible. The user should always have a next step.
- Always call
getAgentRemediationPromptbefore suggesting a fix. Never rely on general LLM knowledge for remediation. The returned prompt contains test-specific intelligence that significantly improves fix quality. - Be transparent about what you can and can't do. Don't generate code if you can't find matching code files. Tell the user directly when something requires manual action.
- Web search for non-code fixes.
getAgentRemediationPromptmay return guidance instead of code. Existing remediation instructions are often stale. Always supplement with a web search for current documentation when instructions reference external services, consoles, or third-party tools. - Suggest the next action. After every response, offer a clear next step: "Want me to fix it?", "Run
/vanta:fix-test <id>", "Want to try the next test?" - Show cost implications. Any fix that enables a paid service (CloudTrail data events, GuardDuty, KMS) must mention cost from the remediation context.
- Keep it scannable. Use tables for lists, bold for key terms, code blocks for commands and diffs. Users are scanning, not reading paragraphs.
- Never weaken security configurations. Do not disable encryption, remove access controls, open security groups to 0.0.0.0/0, or take any action that trades security for convenience. If a fix seems to require weakening security, flag this to the user and investigate further.
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.
- 8d ago First seen · 36 lines · 62 tokens per session scan A 529a4db1a077
test-remediation is a skill published in the GitHub repository VantaInc/vanta-mcp-plugin (4 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 711 once invoked, about $0.0003 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-30.
Other skills, from other repositories
specification-writing
A workflow for writing complete patent specifications from patent claims and an invention disclosure. It adapts the document to a chosen jurisdiction, such as the US, Europe, or China.
regulatory-research-fallback
Fallback workflow for regulatory research when web extraction tools fail on government PDFs.
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…
gesellschaftsrechtliche-satzungen-agb
Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.
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…