Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add agntcy/dir-mcp/plugin install agntcy-dirWrote 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/agntcy/dir-mcp/configure-dir-mcp)<a href="https://agentmods.dev/skills/agntcy/dir-mcp/configure-dir-mcp"><img src="https://agentmods.dev/badge/skills/agntcy/dir-mcp/configure-dir-mcp/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/agntcy/dir-mcp/configure-dir-mcp"><img src="https://agentmods.dev/badge/skills/agntcy/dir-mcp/configure-dir-mcp.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.00070 | $0.02094 |
| Opus 5 | $0.00035 | $0.01047 |
| Sonnet 5 | $0.00014 | $0.00419 |
| Haiku 4.5 | $0.00007 | $0.00209 |
Grade A, and why
configure-dir-mcp 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 6d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configure dir-mcp
Use this skill to inspect and update the dir-mcp runtime configuration at ~/.config/dir-mcp/config.json (or the path in $DIR_MCP_CONFIG).
1. Find the config file
Resolve the active config path to an absolute path — do not use ~ with your file-read/file-write tools. Those tools open paths literally and do not expand ~, so an edit "to ~/.config/dir-mcp/config.json" can silently create a file named ~ under the current working directory instead of touching the real config. Always resolve first:
echo "${DIR_MCP_CONFIG:-$HOME/.config/dir-mcp/config.json}"
Use the printed absolute path (e.g. /Users/alice/.config/dir-mcp/config.json) for every subsequent read or edit in this skill — never the literal ~/... string.
Read it with that absolute path:
cat "${DIR_MCP_CONFIG:-$HOME/.config/dir-mcp/config.json}"
If the file does not exist, the npm wrapper creates it with defaults on first run. You can also create it manually — see the template in step 4.
2. Understand the options
| Key | Default | Purpose |
|---|---|---|
OASF_API_VALIDATION_SCHEMA_URL |
https://schema.oasf.outshift.com |
OASF schema server used for validation, get_schema, and taxonomy lookups |
DIRECTORY_CLIENT_SERVER_ADDRESS |
0.0.0.0:8888 |
Address of the AGNTCY Directory server (host:port) |
DIRECTORY_CLIENT_AUTH_MODE |
none |
Auth mode for the Directory client — see modes below |
DIRECTORY_CLIENT_AUTH_TOKEN |
(empty) | Pre-issued bearer token; skips interactive login |
DIRECTORY_CLIENT_OIDC_ISSUER |
(empty) | OIDC issuer URL (required for oidc mode) |
DIRECTORY_CLIENT_OIDC_CLIENT_ID |
(empty) | OIDC client ID (required for oidc mode) |
DIRECTORY_CLIENT_SPIFFE_SOCKET_PATH |
(empty) | SPIFFE Workload API socket path (for x509/jwt modes) |
DIRECTORY_CLIENT_SPIFFE_TOKEN |
(empty) | Path to SPIFFE token file (for token mode) |
DIRECTORY_CLIENT_JWT_AUDIENCE |
(empty) | JWT audience claim (for jwt mode) |
DIRECTORY_CLIENT_TLS_CERT_FILE |
(empty) | Client TLS certificate file (for tls mode) |
DIRECTORY_CLIENT_TLS_KEY_FILE |
(empty) | Client TLS private key file (for tls mode) |
DIRECTORY_CLIENT_TLS_CA_FILE |
(empty) | CA certificate for server verification (for tls mode) |
DIRECTORY_CLIENT_TLS_SKIP_VERIFY |
(empty) | Set to true to skip TLS certificate verification |
DIRECTORY_MCP_PATH |
(bundled binary) | Absolute path to the dir-mcp server binary; overrides the binary bundled in the npm package |
DIRECTORY_MCP_VERSION |
(npm package version) | Expected dir-mcp server version; logged at startup for diagnostics |
DIRECTORY_DIRCTL_PATH |
(bundled binary) | Absolute path to the dirctl binary; overrides the binary bundled in the npm package |
DIRECTORY_DIRCTL_VERSION |
(empty) | Expected dirctl version (e.g. 1.6.3); dirctl-auth warns if the installed version does not match |
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.
- 6d ago Changed · +39 tokens per session 48a6aba53bf4
- 10d ago First seen · 174 lines · 31 tokens per session scan A 0037e453eeb8
configure-dir-mcp is a skill published in the GitHub repository agntcy/dir-mcp (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 70 tokens to every session and 2,094 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…