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 Asana/cursor-marketplace-plugin --skill asana-setupgit clone --depth 1 https://github.com/Asana/cursor-marketplace-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/asana/cursor-marketplace-plugin/asana-setup)<a href="https://agentmods.dev/skills/asana/cursor-marketplace-plugin/asana-setup"><img src="https://agentmods.dev/badge/skills/asana/cursor-marketplace-plugin/asana-setup/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/asana/cursor-marketplace-plugin/asana-setup"><img src="https://agentmods.dev/badge/skills/asana/cursor-marketplace-plugin/asana-setup.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.00021 | $0.00685 |
| Opus 5 | $0.00010 | $0.00342 |
| Sonnet 5 | $0.00004 | $0.00137 |
| Haiku 4.5 | $0.00002 | $0.00068 |
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 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Asana MCP Setup
Purpose
This skill ensures the Asana MCP server is correctly authenticated before any Asana tools are used.
The Asana MCP connection requires two credentials from a registered Asana OAuth app:
ASANA_CLIENT_IDASANA_CLIENT_SECRET
These must be set as environment variables in the user's shell profile.
When to run this skill
Run this skill automatically if:
- The user asks to connect to Asana
- The user asks to use any Asana tool and the MCP connection fails
- The user says something like "set up Asana" or "configure Asana"
Steps
1. Check if credentials are set
Check whether ASANA_CLIENT_ID and ASANA_CLIENT_SECRET are set in the user's environment. You can do this by running:
echo $ASANA_CLIENT_ID
echo $ASANA_CLIENT_SECRET
If both return non-empty values, skip to Step 4.
2. Guide the user to create an Asana OAuth app
If credentials are missing, tell the user:
To connect Cursor to Asana, you need to register an OAuth app in Asana's developer console. Here's how:
- Go to https://app.asana.com/0/my-apps
- Click Create new app and select "MCP App" as the app type
- Give it a name (e.g. "Cursor MCP")
- Under OAuth, add this redirect URI:
cursor://anysphere.cursor-mcp/oauth/callback- Copy your Client ID and Client Secret
3. Help the user set environment variables
Once the user has their credentials, instruct them to add these lines to their shell profile:
For zsh (macOS default) — add to ~/.zshrc:
export ASANA_CLIENT_ID="your_client_id_here"
export ASANA_CLIENT_SECRET="your_client_secret_here"
For bash — add to ~/.bashrc or ~/.bash_profile:
export ASANA_CLIENT_ID="your_client_id_here"
export ASANA_CLIENT_SECRET="your_client_secret_here"
For Windows (WSL) — add to ~/.bashrc:
export ASANA_CLIENT_ID="your_client_id_here"
export ASANA_CLIENT_SECRET="your_client_secret_here"
After saving, tell the user to run:
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 · 91 lines · 21 tokens per session scan A d90afcfa7bcd
asana-setup is a skill published in the GitHub repository Asana/cursor-marketplace-plugin (0 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 685 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.