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 vinilana/dotcontext --skill security-auditgit clone --depth 1 https://github.com/vinilana/dotcontextWrote 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/vinilana/dotcontext/security-audit)<a href="https://agentmods.dev/skills/vinilana/dotcontext/security-audit"><img src="https://agentmods.dev/badge/skills/vinilana/dotcontext/security-audit/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/vinilana/dotcontext/security-audit"><img src="https://agentmods.dev/badge/skills/vinilana/dotcontext/security-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00010 | $0.01358 |
| Opus 5.5 | $0.00004 | $0.00543 |
| Sonnet 5.5 | $0.00002 | $0.00272 |
| Haiku 4.5 | $0.00001 | $0.00136 |
Grade A, and why
Security Audit 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Audit
Security review checklist specific to the @dotcontext/cli CLI tool and MCP server.
When to Use
- Reviewing code that handles API keys or credentials
- Adding a new AI provider integration
- Changing the MCP server's file access or path resolution
- Modifying the export/sync service that writes files
- Evaluating dependencies for vulnerabilities
- Before a release (especially major or minor versions)
Threat Model
The @dotcontext/cli tool has a specific threat surface:
| Asset | Risk | Location |
|---|---|---|
| AI provider API keys | Exposure via logs, config files, or provider helpers | src/services/ai/providerFactory.ts, env vars |
| File system access | Path traversal, reading outside repo boundaries | src/services/mcp/gateway/explore.ts, readFileTool.ts |
| MCP server stdio | Command injection via tool parameters | src/services/mcp/mcpServer.ts |
| Generated scaffold content | Inclusion of secrets in .context/ output |
src/services/ai/tools/, src/services/autoFill/, src/generators/ |
| User repository content | Unintended exposure via exported context | src/services/export/, src/services/sync/ |
| Dependencies | Supply chain vulnerabilities | package.json |
Security Checklist
API Key Handling
- API keys are read from environment variables or CLI flags, never hardcoded
- Provider env access goes through
src/services/ai/providerFactory.tshelpers - Keys are never logged, even in verbose mode
- Keys are never written to scaffold files or
.context/output - Content sanitization (
src/utils/contentSanitizer.ts) strips potential secrets from generated content -
.envfiles are in.gitignore
File System Security
- File paths are resolved with
path.resolve()before access - Path traversal is prevented: no
../sequences that escape the repo root -
readFileTool.tsvalidates paths are within the project boundary - MCP explore tool's
readaction bounds access to the repo path - Glob patterns in
listandsearchactions respect exclude patterns - Generated files are written only to the configured output directory (
.context/by default)
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 · 129 lines · 10 tokens per session scan A 7f4d015f2fdc
Security Audit is a skill published in the GitHub repository vinilana/dotcontext (573 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 1,358 once invoked, about $0.0000 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.