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-usagegit 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-usage)<a href="https://agentmods.dev/skills/asana/cursor-marketplace-plugin/asana-usage"><img src="https://agentmods.dev/badge/skills/asana/cursor-marketplace-plugin/asana-usage/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-usage"><img src="https://agentmods.dev/badge/skills/asana/cursor-marketplace-plugin/asana-usage.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.00026 | $0.00306 |
| Opus 5.5 | $0.00010 | $0.00122 |
| Sonnet 5.5 | $0.00005 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
asana-usage 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
Asana Usage Best Practices
Before using Asana tools
Always verify the MCP connection is active. If tools are unavailable, run the asana-setup skill first.
Working with tasks
- When creating tasks, always confirm the target project with the user before creating
- When searching, prefer specific project or section filters over broad workspace searches
- Always show the user a summary of what will be created or modified before taking action
- For bulk operations (creating multiple tasks), list them all first and ask for confirmation
Working with projects
- Never delete a project without explicit user confirmation
- When duplicating a project, confirm the new name before proceeding
- Section names matter — confirm with the user before moving tasks between sections
Handling ambiguity
- If the user references "my project" or "the team" without being specific, ask which project they mean before taking action
- If multiple workspaces exist, ask the user which one to use before searching or creating
Error handling
- If an MCP tool call fails with an auth error, run the
asana-setupskill - If a task or project GID is not found, do not guess — ask the user to verify the resource exists
- Rate limit errors: wait 10 seconds and retry once before reporting the error to the user
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 · 35 lines · 26 tokens per session scan A 6b3fddd179be
asana-usage is a skill published in the GitHub repository Asana/cursor-marketplace-plugin (2 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 306 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 skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.