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.
git clone --depth 1 https://github.com/agntcy/dir-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/rules/agntcy/dir-mcp/dirctl-auth)<a href="https://agentmods.dev/rules/agntcy/dir-mcp/dirctl-auth"><img src="https://agentmods.dev/badge/rules/agntcy/dir-mcp/dirctl-auth/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/rules/agntcy/dir-mcp/dirctl-auth"><img src="https://agentmods.dev/badge/rules/agntcy/dir-mcp/dirctl-auth.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.00028 | $0.00287 |
| Opus 5.5 | $0.00011 | $0.00115 |
| Sonnet 5.5 | $0.00006 | $0.00057 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
dirctl-auth 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.
What it actually says
dirctl Authentication
When the user asks to log in to the Directory, authenticate with dirctl, get a token, run dirctl auth login, or fix auth errors from the MCP tools, follow the dirctl-auth skill.
Binary lookup
Never run which dirctl or scan PATH. The binary must come from DIRECTORY_DIRCTL_PATH in mcp.json's env block or the bundled binary set by the npm wrapper. If neither is available, instruct the user to set DIRECTORY_DIRCTL_PATH there.
Login always requires the browser
dirctl auth login always uses the browser-based PKCE flow — never add --no-browser to try to complete login yourself. Logging in requires a human to authenticate in a real browser session; no combination of flags or endpoints lets this be finished without the user. Tell the user a browser window has opened and wait for them to complete it there.
When to trigger
- "log in to the Directory"
- "authenticate with dirctl"
- "dirctl auth login"
- "get a token" / "refresh my token"
- MCP tools return auth or permission errors and the auth mode is
oidc
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 Changed · +4 lines 70f9887a5c3e
- 2mo ago First seen · 20 lines · 28 tokens per session scan A 76f00dd965b4
dirctl-auth is a cursor rule published in the GitHub repository agntcy/dir-mcp (4 stars, last pushed 3d ago), licensed Apache-2.0. It adds 28 tokens to every session and 287 once invoked, about $0.0001 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-31.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.