Claude Code Plugins Directory is a marketplace containing plugins for Claude Code, including tools, commands, skills, agents, hooks, and model context servers. Claude Code users browse it to install Anthropic-maintained or approved third-party extensions.
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/anthropics/claude-plugins-officialWrote 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/commands/anthropics/claude-plugins-official/asana-setup)<a href="https://agentmods.dev/commands/anthropics/claude-plugins-official/asana-setup"><img src="https://agentmods.dev/badge/commands/anthropics/claude-plugins-official/asana-setup.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.00022 | $0.00491 |
| Opus 5 | $0.00011 | $0.00246 |
| Sonnet 5 | $0.00004 | $0.00098 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
asana-setup 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- asana-setup — 100% identical, 0 lines differ
What it actually says
The user wants to connect Claude Code to Asana's V2 MCP server. Guide them through the one-time setup below. Do NOT run claude mcp add yourself — the --client-secret prompt needs a real terminal (a hidden TTY prompt), so the user must run it in their own terminal.
Their Asana OAuth Client ID (if provided): $1
Print these steps clearly, substituting the Client ID into the command if $1 is non-empty (otherwise leave the YOUR_CLIENT_ID placeholder):
Step 1 — Create an Asana OAuth app (one time)
- Open the Asana developer console: https://app.asana.com/0/my-apps
- Create a new app.
- Under OAuth, add this exact Redirect URL:
http://localhost:8080/callback - Copy the Client ID and Client Secret.
Note: localhost is correct — Claude Code is a local client and catches the OAuth callback on your own machine. Asana's V2 server does not support Dynamic Client Registration, so you must bring your own client_id + client_secret.
Step 2 — Add the server (run this in YOUR terminal)
claude mcp add --transport http \
--client-id YOUR_CLIENT_ID --client-secret \
--callback-port 8080 \
asana https://mcp.asana.com/v2/mcp
--client-secret(no value) triggers a hidden prompt; paste the Client Secret there. It is stored in your OS keychain.- The port in
--callback-portmust match thehttp://localhost:8080/callbackredirect you registered.
Step 3 — Authenticate & verify
- On first use, Claude Code opens your browser for Asana consent — approve it.
- Run
/mcpand confirmasanashows as connected. - Test it: ask "list my Asana workspaces".
After printing the steps, offer to help troubleshoot if they hit invalid_redirect_uri (redirect/port mismatch) or invalid_client (wrong id/secret).
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.
- 7d ago First seen · 43 lines · 22 tokens per session scan A 3d4d6079c76c
asana-setup is a command published in the GitHub repository anthropics/claude-plugins-official (35,945 stars, last pushed yesterday), licensed Apache-2.0. It adds 22 tokens to every session and 491 once invoked, about $0.0001 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 commands, from other repositories
release
Git geçmişinden hedef kitleye uygun sürüm notları oluştur.
spec-forge
Use when generating software specifications — full chain (Idea→Decompose→Tech Design + Feature Specs) or individual documents.
dd-spec-test
Generate test spec (requires confirmed status).
dd-init
Initialize product documentation structure in current directory.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.