What is asana-sweep-setup?

A setup assistant for asana-sweep, a tool that connects repository changes with Asana tasks and GitLab settings. It derives configuration, writes a repository config file, and validates it with a dry run.

Use it to configure asana-sweep, identify the GitLab project and base branch, set task-based scope rules, and preview the result safely.

It avoids manually assembling repository and task-tracking settings and lets you review the inferred scope before using the tool.

asana-sweep-setup — Skill for Claude Code by YCyrus

Install

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.

Any agent

npx skills add YCyrus/asana-sweep --skill asana-sweep-setup

Clone the repo

git clone --depth 1 https://github.com/YCyrus/asana-sweep

Made for: Claude Code.

Or install asana-sweep, the plugin that ships this one along with the rest of its 3 skills, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ycyrus/asana-sweep/asana-sweep-setup/github.svg)](https://agentmods.dev/skills/ycyrus/asana-sweep/asana-sweep-setup)

Your own site

<a href="https://agentmods.dev/skills/ycyrus/asana-sweep/asana-sweep-setup"><img src="https://agentmods.dev/badge/skills/ycyrus/asana-sweep/asana-sweep-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ycyrus/asana-sweep/asana-sweep-setup"><img src="https://agentmods.dev/badge/skills/ycyrus/asana-sweep/asana-sweep-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,008 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00066	$0.01008
Opus 5	$0.00033	$0.00504
Sonnet 5	$0.00013	$0.00202
Haiku 4.5	$0.00007	$0.00101

Measured 3d ago against content hash 52a1e92fabd1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

asana-sweep-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 3d 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.

skills/asana-sweep-setup/SKILL.md · 55 lines

How it starts

The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Set up asana-sweep

Create a safe first draft of asana-sweep.config.json in the current repository. Derive everything available from the repository and Asana before asking the user. The setup is complete when the user has confirmed the inferred scope, the config is written, and an asana-sweep dry run has been presented.

1. Inspect without changing anything

Read asana-sweep.config.example.json from the installed plugin and preserve its complete schema, including window_days and harness.
Check whether asana-sweep.config.json already exists. Read it now, but do not overwrite it during discovery.
Run git remote -v. Prefer origin; if there is no origin and exactly one distinct remote repository exists, use it. Parse the repository path from either form, remove a trailing .git, and preserve nested groups:
- SSH/scp: git@host:group/repo.git -> group/repo
- SSH URL: ssh://git@host/group/repo.git -> group/repo
- HTTPS: https://host/group/repo.git -> group/repo
Run git symbolic-ref --short refs/remotes/origin/HEAD and remove the origin/ prefix for gitlab.base_branch. Ask the user only if it fails or points at a different remote than the chosen repository.
Call asana_list_workspaces. Use the only workspace automatically; when several are returned, show their names and gids and ask the user to choose.
Test the selected workspace with asana_search_tasks. Set paid_workspace to false only when the response is payment_required; otherwise set it to true.
Use these path defaults unless the repository already has a clear, established plans/documentation directory; in that case keep all three files together under that convention:
- state_file: docs/plans/.asana-sweep-state.json
- summary_file: docs/plans/.asana-sweep-last-summary.md
- plans_dir: docs/plans

If a remote, workspace, or path convention remains ambiguous after inspection, explain the evidence and ask only for the unresolved choice.

Read the full file on GitHub · 55 lines

Changes

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.

3d ago First seen · 55 lines · 66 tokens per session scan A 52a1e92fabd1

Subscribe to this mod's changes

asana-sweep-setup is a skill published in the GitHub repository YCyrus/asana-sweep (2 stars, last pushed 4d ago), licensed MIT. It adds 66 tokens to every session and 1,008 once invoked, about $0.0003 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-09-08.

Git and workflow Project management ai-agent asana automation claude-code-plugin gitlab

gitlab-mr

GitLab merge request operations. ALWAYS use this skill when user wants to: (1) list merge requests, (2) view MR details, (3) create new MRs, (4) approve/merge MRs, (5) checkout MR branches, (6) add notes/comments, (7) rebase MRs.

grandcamel/GitLab-Assistant-Skills · 73 tokens

catchup

Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.

oliver-kriska/claude-elixir-phoenix · 48 tokens

work

Dispatch a tracker ticket into an isolated worktree and drive it autonomously to an open pull request, then stop for review. Pass interactive to brainstorm the ticket with a human before planning it, or a sentence of editorial direction as a rider. Use when asked to work a ticket end-to-end.

mikestankavich/claude-ship-workflow · 0 tokens

asana-sweep-setup