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 workato-devs/recipe-skills --skill asana-recipesgit clone --depth 1 https://github.com/workato-devs/recipe-skillsWrote 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/workato-devs/recipe-skills/asana-recipes)<a href="https://agentmods.dev/skills/workato-devs/recipe-skills/asana-recipes"><img src="https://agentmods.dev/badge/skills/workato-devs/recipe-skills/asana-recipes/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/workato-devs/recipe-skills/asana-recipes"><img src="https://agentmods.dev/badge/skills/workato-devs/recipe-skills/asana-recipes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Tool Misuse · line 79 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
- medium Tool Misuse · line 92 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
- medium Tool Misuse · line 93 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
- medium Tool Misuse · line 101 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
- medium Tool Misuse · line 102 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
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.00044 | $0.02056 |
| Opus 5 | $0.00022 | $0.01028 |
| Sonnet 5 | $0.00009 | $0.00411 |
| Haiku 4.5 | $0.00004 | $0.00206 |
Grade A, and why
asana-recipes scanned grade A with 1 finding 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
3. **Use API endpoint trigger** for testability via curl How it starts
The opening of the file, as written. The whole thing — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Asana Recipes Skill - Agent Instructions
DEPENDENCY: Load the
workato-recipesbase skill first if not already loaded. This skill requires the base Workato knowledge for triggers, control flow, datapills, formulas, and recipe structure.
This skill provides Asana-specific knowledge for generating Workato recipes. It extends the workato-recipes base skill and focuses on Asana-specific patterns, including:
- Native Asana connector (
provider: "asana") — 16 native actions for common operations - Adhoc HTTP for Asana REST API endpoints not covered by native actions
CRITICAL: Pre-Generation Checklist
For EXISTING projects:
- Read existing Asana
.recipe.jsonfiles to understand local patterns - Check the config section for the connection name already in use
For GREENFIELD projects:
- Use skill templates — see
templates/create-task.json,templates/get-task.json,templates/search-tasks.json - Use descriptive UUIDs — e.g.,
create-task-001,search-tasks-002
ALWAYS:
- Ask for connection name — exact name of Asana connection in Workato
- Confirm workspace/project — which Asana workspace and project GIDs?
- Use API endpoint trigger for testability via curl
- Use descriptive UUIDs — never copy random hex UUIDs from existing recipes
- Include opt_fields parameter — most Asana GET endpoints accept
opt_fieldsto select returned fields
Table of Contents
- When to Use This Skill
- Asana Config Requirements
- Native Connector Guidance
- Asana Datapill Paths
- Adhoc HTTP for Extended API Coverage
- Common Patterns
- Validation
- Templates
- References
When to Use This Skill
Use this skill when building Workato recipes that:
- Create, read, update, or delete Asana resources (tasks, projects, goals, etc.)
- Search or list Asana resources with filtering
- Manage relationships between Asana resources (task→project, user→team, etc.)
- React to Asana events (task changed, project updated, etc.)
- Handle operations not covered by native actions via adhoc HTTP
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 235 lines · 44 tokens per session scan A e038ef6c8851
asana-recipes is a skill published in the GitHub repository workato-devs/recipe-skills (18 stars, last pushed 12d ago), licensed MIT. It adds 44 tokens to every session and 2,056 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.